Status : Failure -Test failed: IO Error: The Network Adapter could not establish the connection (CONNECTION_ID=)
Please check the firewall , allow database port at firewall level and test using
telnet IP db_port
Status : Failure -Test failed: IO Error: The Network Adapter could not establish the connection (CONNECTION_ID=)
Please check the firewall , allow database port at firewall level and test using
telnet IP db_port
Query to Check Big Endian or Little Endian format for your Oracle Database
Login into Oracle database
SQL> select * from v$transportable_platform;
PLATFORM_ID PLATFORM_NAME ENDIAN_FORMAT CON_ID
----------- ----------------------------------------- -------------- ----------
1 Solaris[tm] OE (32-bit) Big 0
2 Solaris[tm] OE (64-bit) Big 0
7 Microsoft Windows IA (32-bit) Little 0
10 Linux IA (32-bit) Little 0
6 AIX-Based Systems (64-bit) Big 0
3 HP-UX (64-bit) Big 0
5 HP Tru64 UNIX Little 0
4 HP-UX IA (64-bit) Big 0
11 Linux IA (64-bit) Little 0
15 HP Open VMS Little 0
8 Microsoft Windows IA (64-bit) Little 0
9 IBM zSeries Based Linux Big 0
13 Linux x86 64-bit Little 0
16 Apple Mac OS Big 0
12 Microsoft Windows x86 64-bit Little 0
17 Solaris Operating System (x86) Little 0
18 IBM Power Based Linux Big 0
19 HP IA Open VMS Little 0
20 Solaris Operating System (x86-64) Little 0
21 Apple Mac OS (x86-64) Little 0
20 rows selected.
SQL>
On Linux - 12c db
====================
SQL> select platform_id from v$database;
PLATFORM_ID
-----------
13
SQL>
SQL> COL "Source" FORM a32
SQL> COL "Compatible Targets" FORM a40
select d.platform_name "Source", t.platform_name "Compatible Targets", endian_format
from v$transportable_platform t, v$database d where t.endian_format = (select endian_format from v$transportable_platform t, v$database d where d.platform_name = t.platform_name)
order by "Compatible Targets"
/SQL> 2 3 4
Source Compatible Targets ENDIAN_FORMAT
-------------------------------- ---------------------------------------- --------------
Linux x86 64-bit Apple Mac OS (x86-64) Little
Linux x86 64-bit HP IA Open VMS Little
Linux x86 64-bit HP Open VMS Little
Linux x86 64-bit HP Tru64 UNIX Little
Linux x86 64-bit Linux IA (32-bit) Little
Linux x86 64-bit Linux IA (64-bit) Little
Linux x86 64-bit Linux x86 64-bit Little
Linux x86 64-bit Microsoft Windows IA (32-bit) Little
Linux x86 64-bit Microsoft Windows IA (64-bit) Little
Linux x86 64-bit Microsoft Windows x86 64-bit Little
Linux x86 64-bit Solaris Operating System (x86) Little
Linux x86 64-bit Solaris Operating System (x86-64) Little
12 rows selected.
SQL>
On Windows - 12c db
====================
SQL> select platform_id from v$database;
PLATFORM_ID
-----------
12
SQL>
SQL>
SQL>
SQL> COL "Source" FORM a32
SQL> COL "Compatible Targets" FORM a40
SQL> select d.platform_name "Source", t.platform_name "Compatible Targets", endian_format
2 from v$transportable_platform t, v$database d where t.endian_format = (select endian_format from v$transportable_platform t, v$database d where d.platform_name = t.platform_name)
3 order by "Compatible Targets"
4 /
Source Compatible Targets ENDIAN_FORMAT
-------------------------------- ---------------------------------------- --------------
Microsoft Windows x86 64-bit Apple Mac OS (x86-64) Little
Microsoft Windows x86 64-bit HP IA Open VMS Little
Microsoft Windows x86 64-bit HP Open VMS Little
Microsoft Windows x86 64-bit HP Tru64 UNIX Little
Microsoft Windows x86 64-bit Linux IA (32-bit) Little
Microsoft Windows x86 64-bit Linux IA (64-bit) Little
Microsoft Windows x86 64-bit Linux x86 64-bit Little
Microsoft Windows x86 64-bit Microsoft Windows IA (32-bit) Little
Microsoft Windows x86 64-bit Microsoft Windows IA (64-bit) Little
Microsoft Windows x86 64-bit Microsoft Windows x86 64-bit Little
Microsoft Windows x86 64-bit Solaris Operating System (x86) Little
Microsoft Windows x86 64-bit Solaris Operating System (x86-64) Little
12 rows selected.
SQL>
Oracle Database Releases and Support Timelines
Currently Oracle 19c database version is stable and long term support
Migrate database workload to Cloud
When Migrating database and application to cloud ,it is very important to keep in mind the business goals ,application and database capabilities and cost of migration .
There are different strategies for different application and database migrations goals .
Same administration experience as on-premise
Full Control over the environment
All feature is available
All version is supported
Optimized Architecture
Database Install and Maintenance
Automated Patching & Upgrade
Automated Backup
High Availability
OS Patching & Maintenance
Scaling
Amazon Aurora
Amazon Redshift
PostgreSQL
Other database engine
Eliminate Oracle Licensing Cost
Cloud Database Migration Lifecycle
Migration to cloud have two major phase :-
Migration Lifecycle
========================
Migration Readiness Assessment
Understand Business acceptation
Note down current know issue, pain area & challenge
Total Cost Of ownership (TCO)
Application Dependency Mapping
Compliance & Risk
Application Portfolio Assessment
Target Architecture
Operating Model
Build Cloud Landing Zone
Migration Plan
Migration Wave Sequencing
Migrate Workload
Validate Migrated Workload
Cutover
Decommission
Cost Optimization
Performance Optimization
Recommended Best Practice
Backup setup + Etc.
Documentation & Knowledge Sharing
High Level Migration Timeline
=================================
*Timeline will be change and depends upon inventory and complexity
Oracle Database Migration Tools & Techniques
Oracle Native Migrations Tools
====================================
• Data Pump
• Transportable Tablespaces
• Full Transportable Export/Import
• Data Guard
• Incremental Backups
• Oracle GoldenGate
• RMAN
AWS Native Migration Tools
=================================
• Database Migration Service (DMS)
• CloudEndure
• AWS Application Migration Service
Oracle database Error ORA-10458: standby database requires recovery
ORA-01196: file 1 is inconsistent due to a failed media recovery session
ORA-01110: data file 1
SQL> set numwidth 30;
SQL> set pagesize 50000;
SQL> alter session set nls_date_format = 'DD-MON-RRRR HH24:MI:SS';
select status,checkpoint_change#,checkpoint_time, resetlogs_change#, resetlogs_time, count(*), fuzzy from v$datafile_header group by status,checkpoint_change#,checkpoint_time, resetlogs_change#, resetlogs_time, fuzzy;
Session altered.
SQL>
STATUS CHECKPOINT_CHANGE# CHECKPOINT_TIME RESETLOGS_CHANGE# RESETLOGS_TIME COUNT(*) FUZ
------- ------------------------------ -------------------- ------------------------------ -------------------- ------------------------------ ---
ONLINE 2472666 26-MAY-2021 11:19:09 1408558 29-APR-2021 11:19:37 4 YES
SQL> select min(fhrba_Seq), max(fhrba_Seq) from X$KCVFH;
MIN(FHRBA_SEQ) MAX(FHRBA_SEQ)
------------------------------ ------------------------------
63 63
SQL>
SQL> SELECT SEQUENCE#, APPLIED FROM V$ARCHIVED_LOG;
SEQUENCE# APPLIED
---------- ---------
1 NO
2 NO
20 YES
21 YES
19 YES
22 YES
23 YES
24 YES
25 YES
26 YES
27 YES
28 YES
29 YES
30 YES
31 YES
32 YES
33 YES
34 YES
36 YES
35 YES
38 YES
40 YES
41 YES
39 YES
37 YES
42 YES
43 YES
44 YES
45 YES
46 YES
47 YES
47 YES
46 YES
48 YES
48 YES
49 YES
49 NO
50 NO
50 YES
52 YES
51 YES
53 YES
54 YES
55 YES
56 YES
57 YES
58 YES
59 YES
60 YES
61 YES
62 YES
SQL>
SQL> alter database open read only;
alter database open read only
*
ERROR at line 1:
ORA-10458: standby database requires recovery
ORA-01196: file 1 is inconsistent due to a failed media recovery session
ORA-01110: data file 1: '/u01/app/oracle/oradata/india_stby/system01.dbf'
SQL>
SQL>
SQL> recover standby database;
ORA-00279: change 2472666 generated at 05/26/2021 11:19:09 needed for thread 1
ORA-00289: suggestion :
/u01/app/oracle/fra/INDIA_STBY/archivelog/2021_05_27/o1_mf_1_63_%u_.arc
ORA-00280: change 2472666 for thread 1 is in sequence #63
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01196: file 1 is inconsistent due to a failed media recovery session
ORA-01110: data file 1: '/u01/app/oracle/oradata/india_stby/system01.dbf'
ORA-01112: media recovery not started
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH;
Database altered.
SQL> alter database open read only;
Database altered.
SQL> select * from hr.abc;
ID NAME
---------- --------------------------------------------------
2 From standby after primary
1 A
3 from primary after convert
SQL> select name ,open_mode ,database_role from v$database;
NAME OPEN_MODE DATABASE_ROLE
--------- -------------------- ----------------
INDIA READ ONLY PHYSICAL STANDBY
SQL>
SQL>
SQL>
SQL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL>
SQL> startup
ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
ORACLE instance started.
Total System Global Area 1048576000 bytes
Fixed Size 8628640 bytes
Variable Size 369100384 bytes
Database Buffers 662700032 bytes
Redo Buffers 8146944 bytes
Database mounted.
Database opened.
SQL> select name ,open_mode ,database_role from v$database;
NAME OPEN_MODE DATABASE_ROLE
--------- -------------------- ----------------
INDIA READ ONLY PHYSICAL STANDBY
We can open database in read write mode using below command and this is also called manual failover
SQL> alter database activate standby database;
Business & Work Keyword Template Style / Use Case Presentation Business decks, pitches, school slides Report Annual reports, whitepapers...