Quantcast
Channel: Doyensys Allappsdba Blog..
Viewing all 1640 articles
Browse latest View live
↧

Oracle EBS R12 changing IP address

January 14, 2017, 10:56 pm
$
0
0
Oracle EBS R12 changing IP address

1)perl $AD_TOP/bin/adgentns.pl appspass=apps contextfile=$APPL_TOP/admin/<SID>_hostname.xml -removeserver

2)connect with sqlplus apps/apps and run the following
begin
FND_NET_SERVICES.remove_server('<SID>', '<hostname>');
end;
/
commit;
/

3) Run autoconfig on application tier

4) Check fnd_nodes to see ip 's are reflected...
select node_id, platform_code, support_db D, support_cp C, support_admin A, support_forms F,
support_web W, node_name, server_id, server_address, domain, webhost, virtual_ip
from fnd_nodes
order by node_id;


Look for the hardcoded old IP Address in the following files on the DB tier
a) listener.ora
b) tnsnames.ora (Local Naming) or check if any other naming method is used to resolve address.
Check if any of the parameter using the old IP Address



↧
Search

ORA-00845:MEMORY_TARGET not supported on this system

January 14, 2017, 10:57 pm
$
0
0
Error:
sql> startup
ORA-00845: MEMORY_TARGET not supported on this system


Solution:
Increase the size of /dev/shm

To check the size of /dev/shm
# df -h
Filesystem    Size   Used  Avail  Use%  Mounted on
/dev/sda3     7.6G   4.4G  2.9G  61%    /
tmpfs         504M   76K   504M  1%     /dev/shm
/dev/sda1     194M   25M   160M   14%   /boot

To increase the size
# mount -o remount,size=3G /dev/shm

Verify the size
# df -h
Filesystem   Size   Used   Avail  Use%  Mounted on
/dev/sda3   7.6G    4.4G   2.9G   61%   /
tmpfs       3G      1007M  2.1G   33%   /dev/shm
/dev/sda1   194M    25M    160M   14%   /boot

To make permanent changes to your file system update your fstab
# vi /etc/fstab
tmpfs  /dev/shm  tmpfs  defaults,size=3G  0 0

Update the new fstab file

# mount -a
↧
↧

ORACLE FORMS GENERAL EXCEPTION ERROR

January 14, 2017, 10:59 pm
$
0
0
ERROR:
“General Exception”
“ExitException: Unable to load resource: http://<HTTPS_PORT>/forms/java/extensions.jnlp”

CAUSE:
HTTPS Java Web Start issue
SOLUTION:
To fix this problem, you will need to add the following parameter inside your config section in formsweb.cfg which is configured for Java Web Start:


webstart_codebase=http://<host>:<HTTP_PORT>/forms/java
↧

Error: The database SID you have specified,orcl, is Already present on this Host. Please specify a SID that is unique on this Host

January 15, 2017, 3:50 am
$
0
0
When we create the database with the same name we are creating he below error.

Error: The database SID you have specified,orcl, is Already present on this Host. Please specify a SID that is unique on this Host

                                             

Cause: 

You have probably previously created database with the same name and have removed it but the traces of it still remain



Solution: 

Open /etc/oratab file in edit mode and remove the line containing SID that is causing an error message.

Another place to look would be $ORACLE_BASE/oraInventory/ContentsXML/inventory.xml - this file could also contain an entry with the offending SID
↧

ORA-12899: value too large for column DATA1 (actual: 35, maximum: 70)

January 15, 2017, 7:24 am
$
0
0
Details:

1. Used expdp and created a dump for the table: SCHEMA. OBJECT_NAME

2. While doing a impdp on the target database :

ORA-02374: conversion error loading table "SCHEMA"."OBJECT_NAME"
ORA-12899: value too large for column DATA1 (actual: 35, maximum: 70)
ORA-02372: data for row: DATA1 : 0X'45737061C3B16F6C1111111111111111111111111111111111'

Solution:

When you describe the table, you will see that the column DATA1 is char(35):

SQL> desc SCHEMA.OBJECT_NAME
 Name                                      Null?    Type
 ----------------------------------------- -------- ----------------------------
 DATA_IDX                                 NOT NULL NUMBER(5)
 DATA_COLUMN                                     NUMBER(5)
 DATA_VALUE                                      NUMBER(5)
 DATA1                                         CHAR(35)

Execute the below to modify the column of the table:

SQL> alter table SCHEMA.OBJECT_NAME modify DATA1 CHAR(70);
Table altered.

Now perform the import using the below command:

impdp directory=DATA_PUMP_DIR dumpfile=SCHEMA.dmp logfile=SCHEMA.log tables=SCHEMA.OBJECT_NAME table_exists_action=truncate

↧
↧

ORA-00055: Maximum Number of DML locks exceeded

January 15, 2017, 7:34 am
$
0
0
The number of DML Locks is set by the initialization parameter DML_LOCKS.
This value will be by default set to small value and results in the error. Increase the value of DML_LOCKS.
Sometimes the issue occurs at peak usage of database.
Change in the parameter file (initSID.ora) For Example: dml_locks = 200
↧

Article 1

January 15, 2017, 10:01 pm
$
0
0

Query to check the pending concurrent requests and the count,status etc.



set lines 300;
set pages 300;
col " CONCURRENT_PROGRAM_NAME" for a60;
col QUEUE_NAME for a12;
col status_code for a12;
select USER_CONCURRENT_PROGRAM_NAME " CONCURRENT_PROGRAM_NAME",concurrent_queue_name "QUEUE_NAME",
 priority,decode(phase_code,'P','Pending') "PHASE",
decode(status_code,'A','Waiting','B','Resuming','C','Normal','D','Cancelled','E','Error','F',
'Scheduled','G','Warning','H','On Hold','I','Normal','M','No Manager','Q','Standby','R','Normal','S',
'Suspended','T','Terminating','U','Disabled','W','Paused','X','Terminated','Z','Waiting') "STATUS",
status_code,count(*) from
apps.fnd_concurrent_worker_requests
where  phase_code='P' and hold_flag!='Y'
and requested_start_date<=sysdate
and concurrent_queue_name<> 'FNDCRM'
and concurrent_queue_name<> 'GEMSPS'
group by
user_CONCURRENT_PROGRAM_NAME,
concurrent_queue_name,priority,phase_code,status_code
order by count(*) desc;
↧

Article 0

January 15, 2017, 10:57 pm
$
0
0

Converting OUT file to xml file using BI publisher.



Step1:

     Get the output file of the required concurrent request from the server.
out file location $APPLCSF/out

Step2:

    Convert the out file to xml file using notepad++ and save it as .xml

Step3:

     Take the concurrent request Short name from the EBS R12

   Concurrent--->Program----->Define

Step4:

       Go to XML Publisher administrator and select template

Put the short name of the concurrent request in code and press enter.

Step5:

   Download the rtf file.

Step6:
 
   Place the xml file and rtf file in the same location.

Step7:

     Open Template viewer(BI Publisher) and open the files .

Step8:

     Click start processing and it will provide the output file.
↧
Search

Activating Cost Manager in Oracle Apps R12

January 16, 2017, 5:30 am
$
0
0
Procedure to activate the cost manager if it is down

Step1:

      Login to Apps with the user,who is having the responsibility to activate the cost manager.

Step2:

    
    Navigate to XXFM-India Local Inventory






Step 4:

Select Launch Interface Managers and 





Step 5:

 Select cost manager from tools and click on launch manager then submit the program





↧
↧

Cannot View Concurrent Manager Log And Out Files in R12

January 16, 2017, 6:29 am
$
0
0

Error:

'APP-FND-1634-The log file &FILENAME does not exist or this program is restricted from reading it'

If the concurrent request has completed then please contact your system administrator.

APP-FND-1636 NO REPORT AVAILABLE FOR THIS CONCURRENT PROCESS

Cause:

Profile Option 'RRA:enabled' setting is not correct.

Solution:

To implement the solution, please execute the following steps:

1. Shut down managers and verify no FNDLIBR processes are running.
2. Go into the responsibility: System Administrator
3. Navigate to profile/system
4. Search for profile 'RRA:enabled' and set the value to Yes.
5. Save
6. Restart the managers
7. Retest the issue.
↧

Enable Trace and take tkprof

January 16, 2017, 6:31 am
$
0
0
Step 1 : Check Request ID from Find Concurrent request screen (In my case Request ID is 1145)

Step 2 : Run below command to find SPID, provide concurrent request ID (1145 in my case) when prompted

SELECT a.request_id, d.sid, d.serial# ,d.osuser,d.process , c.SPID
FROM apps.fnd_concurrent_requests a,
apps.fnd_concurrent_processes b,
v$process c,
v$session d
WHERE a.controlling_manager = b.concurrent_process_id
AND c.pid = b.oracle_process_id
AND b.session_id=d.audsid
AND a.request_id = &Request_ID;

REQUEST_ID        SID    SERIAL# OSUSER           PROCESS    SPID
—————----------------------------------------------------------------------------
   1145                  514            28         applmgr             17794        2987.
.

Step 3.1 : Check and confirm SPID on Database Node
$   ps-ef | grep 2987
  proddb   2987     1  0 13:30:43 ?        0:03 oracledbr12 (LOCAL=NO)

Step 3.2 : Set OSPID (2987 in my case) for ORADEBUG
SQL> oradebug setospid 2987

Step 3.3 : Enable trace for 10046 event with level 12
SQL> oradebug event 10046 trace name context forever, level 12

LEVEL 12 – Both Binds and Waits
LEVEL 8 – Only WAITS
LEVEL 4 – Only BIND Variables

Step 3.4 : Locate Trace file as
SQL>oradebug tracefile_name

/oracle/apps/proddb/10.2.0/admin/prod_CSDoracle/udump/ prod _ora_2987.trc

Wait for 15-20 minutes

Step 4 : Disable trace
SQL> oradebug event 10046 trace name context off

Step 5: Create tkprof file like
$ tkprof prod _ora_2987.trc prod _ora_2987.txt explain=apps/<****>  sort=(exeela,fchela) sys=no ---------------Provide apps password-----------
↧

ORA-24247: network access denied by access control list (ACL)

January 16, 2017, 7:09 am
$
0
0 
Error:
ERROR at line 1:
ORA-29273: HTTP request failed
ORA-24247: network access denied by access control list (ACL)
ORA-06512: at "SYS.UTL_HTTP", line 1491
ORA-06512: at line 1

Workaround:
No access control list (ACL) has been assigned to the target host or the privilege necessary to access the target host has not been granted to the user in the access control list.

Solution:
1)give the privileges to the corresponding schema.

grant execute on utl_http to HR

2)assign the acl for corresponding  hostname (or) IP

exec dbms_network_acl_admin.assign_acl ( acl => 'utl_http.xml', host => '(hostname)',lower_port => null, upper_port => null);

↧

While running autoconfig,we got error ORA-04063: package body "APPS.FND_GLOBAL" has errors has been detected in FND_GSM_UTIL.upload_context_file

January 16, 2017, 9:22 am
$
0
0
Error:

Attempting upload of Context file and templates to database...ERROR: InDbCtxFile.uploadCtx() : Exception : Error executng BEGIN fnd_gsm_util.upload_context_file(:1,:2,:3,:4,:5); END;: 1; Oracle error -4063: ORA-04063: package body "APPS.FND_GLOBAL" has errors has been detected in FND_GSM_UTIL.upload_context_file. 
oracle.apps.ad.autoconfig.oam.InDbCtxFileException: Error executng BEGIN fnd_gsm_util.upload_context_file(:1,:2,:3,:4,:5); END;: 1; Oracle error -4063: ORA-04063: package body "APPS.FND_GLOBAL" has errors has been detected in FND_GSM_UTIL.upload_context_file. 

SQL> alter package apps.FND_GLOBAL compile body; 

Warning: Package Body altered with compilation errors. 

SQL> show errors 
Errors for PACKAGE BODY APPS.FND_GLOBAL: 

LINE/COL ERROR 
-------- ----------------------------------------------------------------- 
2048/11 PL/SQL: SQL Statement ignored 
2050/18 PL/SQL: ORA-04063: view "APPS.FND_USER_RESP_GROUPS" has errors 
SQL> alter view APPS.FND_USER_RESP_GROUPS compile; 

Warning: View altered with compilation errors. 

SQL> 
SQL> 
SQL> show errors view APPS.FND_USER_RESP_GROUPS 
Errors for VIEW APPS.FND_USER_RESP_GROUPS: 

LINE/COL ERROR 
-------- ----------------------------------------------------------------- 
0/0 ORA-04063: view "APPS.WF_USER_ROLE_ASSIGNMENTS_V" has errors 
SQL> 
SQL> 
SQL> alter view APPS.WF_USER_ROLE_ASSIGNMENTS_V compile; 

Warning: View altered with compilation errors. 

SQL> show errors view APPS.WF_USER_ROLE_ASSIGNMENTS_V; 
Errors for VIEW APPS.WF_USER_ROLE_ASSIGNMENTS_V: 

LINE/COL ERROR 
-------- ----------------------------------------------------------------- 
0/0 ORA-00980: synonym translation is no longer valid 

Workaround:

1. Please run:

adjava -mx512m -nojit oracle.apps.fnd.odf2.FndXdfCmp APPLSYS apps APPS apps THIN \
test1.ro.oracle.com:1521:VIS TABLE \
$FND_TOP/patch/115/xdf/wf_local_user_roles.xdf $FND_TOP/patch/115/xdf/xsl changedb=y

2. Validate 'APPS.WF_USER_ROLES'

3. Please run:
adjava -mx512m -nojit oracle.apps.fnd.odf2.FndXdfCmp APPLSYS apps APPS apps THIN \
test1.ro.oracle.com:1521:VIS TABLE \
$FND_TOP/patch/115/xdf/wf_user_role_assignments.xdf $FND_TOP/patch/115/xdf/xsl changedb=y

4. Check if WF_USER_ROLE_ASSIGNMENTS_V is valid.

5. recompile WF_DIRECTORY

6. After that compile the package body also (FND_GLOBAL)

SQL> alter view apps.WF_USER_ROLE_ASSIGNMENTS_V compile; 

View altered. 

SQL> alter view APPS.FND_USER_RESP_GROUPS compile; 

View altered. 

SQL> select object_name,owner,object_type,status from dba_objects where object_name='WF_USER_ROLE_ASSIGNMENTS_V'; 

OBJECT_NAME 
-------------------------------------------------------------------------------- 
OWNER OBJECT_TYPE STATUS 
------------------------------ ------------------- ------- 
WF_USER_ROLE_ASSIGNMENTS_V 
APPS VIEW VALID 


SQL> select object_name,owner,object_type,status from dba_objects where object_name='WF_DIRECTORY'; 

OBJECT_NAME 
-------------------------------------------------------------------------------- 
OWNER OBJECT_TYPE STATUS 
------------------------------ ------------------- ------- 
WF_DIRECTORY 
APPS PACKAGE VALID 

WF_DIRECTORY 
APPS PACKAGE BODY INVALID 

---------------------------------------------------------------------------------------------------------------------------------------- 
OBJECT_NAME 
-------------------------------------------------------------------------------- 
OWNER OBJECT_TYPE STATUS 
------------------------------ ------------------- ------- 
WF_DIRECTORY 
APPS PACKAGE VALID 

WF_DIRECTORY 
APPS PACKAGE BODY VALID

7.  alter package apps.FND_GLOBAL compile body; 

Package body altered. 


↧
↧

How to Manually Remove the Enterprise Manager Grid/Cloud Control Agent

January 16, 2017, 12:15 pm
$
0
0
Steps to remove the agents in 12c:

$AGENT_HOME/bin/emctl stop agent

cd $OMS_HOME/bin

./emcli login -username=sysman

./emcli sync

[oracle@oem bin]$ emcli get_targets |grep Down

Status  Status           Target Type           Target Name
-------------------------------------------------------------------------
0       Down             oracle_database       db1.test.com


./emcli delete_target -name="db1.test.com" -type="oracle_database"


Query
=====

select TARGET_NAME,TARGET_TYPE,PROPERTY_VALUE,PROPERTY_NAME  from mgmt$target_properties where target_name = 'db1.test.com'

no rows selected

↧

OEM Console disappears after clicking Database Name

January 16, 2017, 4:34 pm
$
0
0
Issue:

10g OEM Console disappears after clicking DB name.



And noticed the below error in this location “C:\Users\Doyen\AppData\Local\Temp”

EXCEPTION_ACCESS_VIOLATION (0xc0000005) occurred at PC=0x8077E76

Solution:

Issue because of the permission Issue, run this console as an administrator and test




↧
Search

Deactivate Application Users who were inactive for more than 60 days

January 16, 2017, 11:50 pm
$
0
0
Deactivate Application Users who were inactive for more than 60 days

a.       Create a backup table with the list of users that are inactive for more than 60 days,
create table INACTIVE_USERS_$ORACLE_SID as
select USER_NAME from fnd_user
where END_DATE is null
and LAST_LOGON_DATE < (sysdate - 60)
and USER_NAME not in ('ANONYMOUS','ASGADM','ASGUEST','AUTOINSTALL','BATCHUSER','C10000300','CONCURRENT MANAGER','DISCOADMIN','FEEDER SYSTEM','GUEST','IBE_ADMIN','IBEGUEST','IBE_GUEST','IEXADMIN','INDUSTRY DATA','INITIALSETUP','IRC_EMP_GUEST','IRC_EXT_GUEST','LATESXXTUSER1','MOBILEADM','OAMADMIN','OP_CUST_CARE_ADMIN','OP_SYSADMIN','ORACLE12.0.0','ORACLE12.1.0','ORACLE12.2.0','ORACLE12.3.0','ORACLE12.4.0','ORACLE12.5.0','ORACLE12.6.0','ORACLE12.7.0','ORACLE12.8.0','ORACLE12.9.0','SYSADMIN','UKDISCOUSER','WIZARD','XML_USER','XXNAO')
order by 1 desc;

Note : - Replace $ORACLE_SID with the db name while creating the backup table
I have included few of the seeded users who will not be deactivated.

b.      Run the following PL/SQL Block to deactivate (End Date the user and its respective responsibilities) the application user,

declare
cursor userapps is
select USER_NAME from fnd_user
where END_DATE is null
and LAST_LOGON_DATE < (sysdate - 60)
and USER_NAME not in ('ANONYMOUS','ASGADM','ASGUEST','AUTOINSTALL','BATCHUSER','C10000300','CONCURRENTMANAGER','DISCOADMIN','FEEDER SYSTEM','GUEST','IBE_ADMIN','IBEGUEST','IBE_GUEST','IEXADMIN','INDUSTRY DATA','INITIAL SETUP','IRC_EMP_GUEST','IRC_EXT_GUEST','LATESXXTUSER1','MOBILEADM',
'OAMADMIN','OP_CUST_CARE_ADMIN','OP_SYSADMIN','ORACLE12.0.0','ORACLE12.1.0','ORACLE12.2.0','ORACLE12.3.0','ORACLE12.4.0','ORACLE12.5.0','ORACLE12.6.0',
'ORACLE12.7.0','ORACLE12.8.0','ORACLE12.9.0','SYSADMIN','UKDISCOUSER','WIZARD','XML_USER','XXNAO')
order by 1 desc;

begin
for x in userapps loop
--End date the following users
--dbms_output.put_line(x.USER_NAME);
fnd_user_pkg.updateuser(x_user_name=>x.USER_NAME,x_owner=>'CUST',x_end_date=>SYSDATE);
commit;
end loop;

end;

c.       Run the following PL/SQL Block to reactivate (Remove end date) the application users,


declare
cursor userapps is
select user_name from fnd_user where user_name in (select distinct user_name from INACTIVE_USERS_$ORACLE_SID);----(Mention the backup table name from step a)

begin

for x in userapps loop
fnd_user_pkg.enableuser(x.user_name);
commit;

end loop;

end;
↧

Opening a DR database in Read/Write temporarily using restore points

January 16, 2017, 11:53 pm
$
0
0
Opening a DR database in read write mode

Objective of this document is to convert the DR database (Mount state) into Read Write mode temporarily and restoring it back to sync it up with the PRIMARY database.

DR Environment
For example  take a  two node clustered DR database as follows,
NAME      DB_UNIQUE_NAME                 OPEN_MODE
--------- ------------------------------ --------------------
I****01   DRI****01                      MOUNTED
I****01   DRI****01                      MOUNTED

INSTANCE_NAME    STATUS       HOST_NAME
---------------- ------------ --------------------------------
I****011         MOUNTED      of90.egan.server.com
I****012         MOUNTED      of91.egan.server.com

If the flashback mode is disabled in the database.
The Flashback mode has to be enabled to restore the DR after application installation.

Steps to enable the flashback mode in both the Primary and DR I****01 database.

1.        Enabling Flashback in DR database.

a.        Cancel the recovery in the standby database.
STANDBY>ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;

b.        Then activate the FLASHBACK on the standby database.
STANDBY> alter system set db_flashback_retention_target=1440 scope=both;  #### retention value varies depending on the requirement.
STANDBY>ALTER DATABASE FLASHBACK ON;

c.        Verify the flashback mode,
SQL> select flashback_on from v$database;

2.        Enabling Flashback in the Primary database.

a.        Activate the FLASHBACK on the PRIMARY database.
PRIMARY> alter system set db_flashback_retention_target=1440 scope=both;#### retention value varies depending on the requirement.
PRIMARY> alter database flashback on;

b.        Verify the flashback mode,
SQL> select flashback_on from v$database;

Once the flashback mode is enabled, we shall go ahead and bring the DR in the read write mode.

Steps to open the DR database in Read/Write mode

a.        Stop the recovery in the DR database.
STANDBY>ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;

b.        Check The MRP status,
STANDBY>select PROCESS,CLIENT_PROCESS,THREAD#,SEQUENCE#,BLOCK# from v$managed_standby where process = 'MRP0' or client_process='LGWR';
                                        (or)
host#     ps –ef|grep –imrp


c.        Creating a restore point to flashback the DR DB to the old stage & this will help us to bring back as a standby database.
STANDBY> CREATE RESTORE POINT stby_fb_dri****01 GUARANTEE FLASHBACK DATABASE;## stby_fb_dri****01 is the restore point name

d.        Check the SCN and restore point details in the DR database,
STANDBY> select NAME,SCN,TIME from v$restore_point;

e.        In the Primary database defer the log shipping to the DR,
PRIMARY> ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2=DEFER;

f.         Activate the DR physical standby database and open it in Read/Write mode,
STANDBY>alter database activate standby database;

g.        Check the status of the controlfile_type after changing the DR database in Read/Write
STANDBY>select CONTROLFILE_TYPE from v$database;

h.        Open the DR database in Read/Write mode,
STANDBY> ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE PERFORMANCE;
STANDBY> ALTER DATABASE OPEN;

i.         Opening the DR in node two is optional, if you would like to open it,
NODE 2 STANDBY>ALTER DATABASE OPEN;



Steps to restore the DR

a.        Stop the DR database completely.
srvctl stop database –d I****01

b.        Start one instance to restore the DR to its old state,
STANDBY>startup mount
STANDBY> FLASHBACK DATABASE TO RESTORE POINT stby_fb_dri****01;

c.        Check the controlfile_type of the DR database,
STANDBY> select controlfile_type from v$database;

d.        Change back the DR to Physical Standby database,
STANDBY> ALTER DATABASE CONVERT TO PHYSICAL STANDBY;

e.        Bounce the DR database and bring them to mount,
STANDBY>shutdown immediate
STANDBY>startup mount

f.         Enable the log shipping in the primary database,
PRIMARY> ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2=ENABLE;

g.        Drop the restore point on the standby database,
STANDBY> DROP RESTORE POINT stby_fb_dri****01;

h.        Start the MRP in the DR database,
STANDBY>ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION;





↧
↧

Opening a DR database in read/write mode temporarily using Snapshot Standby

January 16, 2017, 11:57 pm
$
0
0
Opening  a DR database in read write mode using Snapshot Standby method

Objective of this document is to convert a DR database (Mount state) into Read Write mode using Snapshot standby method and restoring it back to sync it up with the PRIMARY database.

DR Environment
The I****01 has a two node clustered DR database as follows,

NAME      DB_UNIQUE_NAME                 OPEN_MODE
--------- ------------------------------ --------------------
I****01   DRI****01                      MOUNTED
I****01   DRI****01                      MOUNTED

INSTANCE_NAME    STATUS       HOST_NAME
---------------- ------------ --------------------------------
I****011         MOUNTED      of90.egan.server.com
I****012         MOUNTED      of91.egan.server.com


The flashback mode is disabled in I****01 database.
The Flashback mode has to be enabled to restore the DR after application installation.

Steps to enable the flashback mode in both the Primary and DR I****01 database.

1.        Enabling Flashback in DR database.

a.        Cancel the recovery in the standby database.
STANDBY>ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;

b.        Then activate the FLASHBACK on the standby database.
STANDBY> alter system set db_flashback_retention_target=1440 scope=both; ### retention value varies depending on the requirement.
STANDBY>ALTER DATABASE FLASHBACK ON;
c.        Verify the flashback mode,
SQL> select flashback_on from v$database;

2.        Enabling Flashback in the Primary database.
a.        Activate the FLASHBACK on the PRIMARY database.
PRIMARY> alter system set db_flashback_retention_target=1440 scope=both;#### retention value varies depending on the requirement.
PRIMARY> alter database flashback on;
b.        Verify the flashback mode,
SQL> select flashback_on from v$database;


Once the flashback mode is enabled, we shall go ahead and bring the DR in the read write mode.

Steps to open the DR database in Read/Write mode using Snapshot Standby

a.        Stop the recovery in the DR database.
STANDBY>ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
b.        Check The MRP status,
STANDBY>select PROCESS,CLIENT_PROCESS,THREAD#,SEQUENCE#,BLOCK# from v$managed_standby where process = 'MRP0' or client_process='LGWR';
                                                                                                                        (or)
host#     ps –ef|grep –imrp


c.        Bring down all instances except oneon which we will be using the conversion commands, and ensure the DR database is in mount state
d.        Convert the Physical standby DR to Snapshot standby DR,
STANDBY>ALTER DATABASE CONVERT TO SNAPSHOT STANDBY;
e.        The DR database will be dismounted after the conversion, so start it.
STANDBY>startup;
f.         The DR will be open in Read/Write mode now.


Steps to convert the Snapshot standby DR to Physical Standby DR

a.        Shutdown all the instances except one on which we will be using the conversion commands.
b.        Ensure that the database is mounted.
c.        Do the conversion of snapshot standby database to physical standby database.
STANDBY>ALTER DATABASE CONVERT TO PHYSICAL STANDBY;
d.        Change back the DR to Physical Standby database,
STANDBY>ALTER DATABASE CONVERT TO PHYSICAL STANDBY;
e.        Bounce the DR database and bring them to mount,
STANDBY>shutdown immediate
STANDBY>startup mount
f.         Enable the log shipping in the primary database,
PRIMARY>ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2=ENABLE;
g.        Start the MRP in the DR database,
STANDBY>ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION;




↧

Article 0

January 16, 2017, 11:58 pm
$
0
0
Creating Cascading standby database

 A cascading standby database is a standby database that receives its redo logs from another standby database, not from the original primary database.

Primary Database      ----- >    Cascading Standby Database     -----> Cascaded Standby Database
(FEMP01 – primary.na)            (DRFEMP01 – standby.na)               (FEMCSD – csdstby.na)       


High Level Steps
·         Create a pfile for the cascading standby FEMCSD.
·         Copy the password file from the DRFEMP01 and rename it to FEMCSD.
·         Create the listener and enter the TNS Entries in the tnsnames.ora
·         Add/modify the log_archive_dest_2 parameter in the Primary(FEMP01) and DR(DRFEMP01) instance
·         Stop the recovery process in the DR database (DRFEMP01)
·         Start the active duplicate standby creation
Low Level Steps
1.       Enable the log_archive_dest_2_state in DRFEMP01.
2.       Start the MRP process in FEMCSD
3.       Enable the monitoring scripts for FEMCSD


a.       Create a pfile for the cascading standby FEMCSD.
*.STANDBY_FILE_MANAGEMENT='AUTO'
*.FAL_SERVER='DRFEMP01'
*.FAL_CLIENT='FEMCSD'
log_archive_config='dg_config=(FEMP01,DRFEMP01,FEMCSD)'
log_archive_dest_1='location=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=FEMCSD'
log_archive_dest_2='service=DRFEMP01valid_for=(STANDBY_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=DRFEMP01'
LOG_ARCHIVE_DEST_STATE_1=ENABLE
LOG_ARCHIVE_DEST_STATE_2=ENABLE
DB_FILE_NAME_CONVERT='+IMPRD_DATA_DG/DRFEMP01','+IMTST_DATA_DG/FEMCSD'
LOG_FILE_NAME_CONVERT='+IMPRD_DATA_DG/DRFEMP01/ONLINELOG','+IMTST_DATA_DG/FEMCSD/ONLINELOG'

b.      Copy the password file from the DRFEMP01 and rename it to FEMCSD.
c.       Create the listener and enter the TNS Entries in the tnsnames.ora
LISTENER_FEMCSD =
  (ADDRESS_LIST=
        (ADDRESS=
         (PROTOCOL=TCP) (HOST=oh61g.example.com) (PORT=1530))
  )
SID_LIST_LISTENER_FEMCSD =
  (SID_LIST =
    (SID_DESC =
      (ORACLE_HOME= /im/tironi/db/FEMCSD/11.2.0.4)
      (SID_NAME = FEMCSD)
    )
  )

TNS ENTRY
FEMCSD =
  (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = oh61g.example.com)(PORT = 1530))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
     (SERVICE_NAME = FEMCSD2)
    )
  )
d.      Add/modify the log_archive_dest_2 parameter in the Primary(FEMP01) and DR(DRFEMP01) instance,
Primary (FEMP01)

alter system set LOG_ARCHIVE_CONFIG='DG_CONFIG=(FEMP01,DRFEMP01,FEMCSD)' scope=both;
alter system set LOG_ARCHIVE_DEST_2='SERVICE=DRFEMP01 LGWR SYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=DRFEMP01';
alter system set LOG_ARCHIVE_DEST_3='SERVICE=FEMCSD LGWR SYNC VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=FEMCSDS'scope=both;
alter system set LOG_ARCHIVE_DEST_STATE_3=DEFER;(This parameter will remain in DEFER state permanently)

DR (DRFEMP01)

alter system set LOG_ARCHIVE_CONFIG='DG_CONFIG=(FEMP01,DRFEMP01,FEMCSD)' scope=both;
alter system set LOG_ARCHIVE_DEST_2='service=FEMP01valid_for=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=FEMP01';
alter system set LOG_ARCHIVE_DEST_3='SERVICE=FEMCSD LGWR SYNC VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=FEMCSD'scope=both;
alter system set LOG_ARCHIVE_DEST_STATE_3=DEFER;(This parameter will remain in DEFER state permanently)

e.      Create necessary directories in the ASM in oh61g.example.com server

a.       Stop the recovery process in the DR database (DRFEMP01)
alter database recover managed standby database using current logfile disconnect from session;





f.        Connect to RMAN with target as DR(DRFEMP01) and auxiliary as Cascaded standby(FEMCSD) and start the active duplicate standby creation.
run
{
ALLOCATE CHANNEL tgt10 TYPE DISK;
ALLOCATE CHANNEL tgt20 TYPE DISK;
ALLOCATE CHANNEL tgt30 TYPE DISK;
ALLOCATE CHANNEL tgt40 TYPE DISK;
ALLOCATE CHANNEL tgt50 TYPE DISK;
ALLOCATE CHANNEL tgt60 TYPE DISK;
ALLOCATE CHANNEL tgt70 TYPE DISK;
ALLOCATE CHANNEL tgt80 TYPE DISK;
ALLOCATE AUXILIARY CHANNEL dup1 TYPE DISK;
ALLOCATE AUXILIARY CHANNEL dup2 TYPE DISK;
ALLOCATE AUXILIARY CHANNEL dup3 TYPE DISK;
ALLOCATE AUXILIARY CHANNEL dup4 TYPE DISK;
ALLOCATE AUXILIARY CHANNEL dup5 TYPE DISK;
ALLOCATE AUXILIARY CHANNEL dup6 TYPE DISK;
ALLOCATE AUXILIARY CHANNEL dup7 TYPE DISK;
ALLOCATE AUXILIARY CHANNEL dup8 TYPE DISK;
duplicate target database for standby from active database nofilenamecheck;
}

g.       After the clone enable the log_archive_state_3 in the DR(DRFEMP01) and start the recovery process,
alter system set log_archive_dest_state_3=ENABLE scope=both;

alter database recover managed standby database using current logfile disconnect from session;

h.      Start the recovery process in the cascaded standby database (FEMCSD),
alter database recover managed standby database using current logfile disconnect from session;


i.         Schedule the DR Sync check and Archive log removal script for the Cascades standby database(FEMCSD)
↧

11g Runinstaller Fails with Error: Java.Lang.Unsatisfiedlinkerror libmawt.so libxext.so.0

January 18, 2017, 12:27 am
$
0
0
11g Runinstaller Fails with Error: Java.Lang.Unsatisfiedlinkerror libmawt.so libxext.so.0 or libmawt.so: libXext.so.6 (Doc ID 1366997.1)
SYMPTOMS
While installing Oracle Database 11.2.0.3 on RHEL 6.2 Linux x86-64 the following error is observed:
$ ./runInstaller
..
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2014-01-02_10-33-37AM. Please wait ..$ Exception in thread "main" java.lang.UnsatisfiedLinkError: /tmp/OraInstall2014-01-02_10-33-37AM/jdk/jre/lib/amd64/xawt/libmawt.so: libXext.so.6: wrong ELF class: ELFCLASS32
       at java.lang.ClassLoader$NativeLibrary.load(Native Method)
       at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1753)
       at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1649)
       at java.lang.Runtime.load0(Runtime.java:769)
       at java.lang.System.load(System.java:968)
       at java.lang.ClassLoader$NativeLibrary.load(Native Method)

CAUSE
Linux:   Library libXext.so.6 is missing
This is possibly due to the package providing the library being corrupt or not installed

SOLUTION
For Linux:
1. Confirm package libXext is installed. When installing 11.2, 64 bit on Linux 64 bit, ensure libXext  64 bit package is installed.And when installing 11.2, 32 bit client on Linux 32 bit /Linux 64 bit then ensure libXext 32 bit package is installed.Run the following Linux command to check if the package is missing:

$ rpm --query --whatprovides 'libXext.so.6'
2.  Re-try invoking the runInstaller (OUI) to install Oracle database 11.2
./runInstaller
↧
Viewing all 1640 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>