Pages

Wednesday, 22 April 2015

RMAN Duplicate fails with "ORA-01276: Cannot add file" error

NSTANCE 'i2'
  GROUP   5 ( '/oracle/oradata/teststby/group_5.264.789509951', '/oracle/oradata/teststby/group_5.296.789509953' ) SIZE 300 M  REUSE,
  GROUP   6 ( '/oracle/oradata/teststby/group_6.263.789509955', '/oracle/oradata/teststby/group_6.297.789509955' ) SIZE 300 M  REUSE,
  GROUP   7 ( '/oracle/oradata/teststby/group_7.274.789509957', '/oracle/oradata/teststby/group_7.298.789509959' ) SIZE 300 M  REUSE,
  GROUP   8 ( '/oracle/oradata/teststby/group_8.299.789510045', '/oracle/oradata/teststby/group_8.275.789510045' ) SIZE 300 M  REUSE
sql statement: ALTER DATABASE ADD LOGFILE

INSTANCE 'i3'
  GROUP  19 ( '/oracle/oradata/teststby/o1_mf_19_9hcqsyb9_.log' ) SIZE 100 M  REUSE,
  GROUP  20 ( '/oracle/oradata/teststby/o1_mf_20_9hcqsyhf_.log' ) SIZE 100 M  REUSE
released channel: prmy1
released channel: prmy2
released channel: prmy3
released channel: prmy4
released channel: aux
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 04/22/2015 02:22:55
RMAN-05501: aborting duplication of target database
RMAN-06136: ORACLE error from auxiliary database: ORA-01276: Cannot add file /oracle/oradata/teststby/o1_mf_19_9hcqsyb9_.log.  File has an Oracle Managed Files file name.

Reason:

OMF parameter set in the database, hence the file name cannot be specified while adding log file

Solution:

Remove following parameters if they are set in parameter file and rerun rman duplicate script

db_create_file_dest
db_create_online_log_dest_1
db_create_online_log_dest_2
db_recovery_file_dest


For more refer Oracle Doc ID:1926495.1

Tuesday, 24 February 2015

UtilSession failed: Prerequisite check "CheckActiveFilesAndExecutables" failed while applying patch

While applying 12c patch, it failed with below error

UtilSession failed: Prerequisite check "CheckActiveFilesAndExecutables" failed while applying patch

[root test.db.com] /oracle/home/oracle$ opatchauto apply /oracle/archivelog/patch/20132450 -ocmrf /oracle/archivelog/patch/unconfig_GI.rsp -nonrolling
OPatch Automation Tool
Copyright (c) 2015, Oracle Corporation.  All rights reserved.

OPatchauto version : 12.1.0.1.5
OUI version        : 12.1.0.2.0
Running from       : /oracle/product/grid/12.1.0

opatchauto log file: /oracle/product/grid/12.1.0/cfgtoollogs/opatchauto/20132450/opatch_gi_2015-02-24_03-25-09_deploy.log

Parameter Validation: Successful

Grid Infrastructure home:
/oracle/product/grid/12.1.0
RAC home(s):
/oracle/product/db/12.1.0

Configuration Validation: Successful

Patch Location: /oracle/archivelog/patch/20132450
Grid Infrastructure Patch(es): 19769473 19769479 19769480 19872484
RAC Patch(es): 19877336 19769479 19769480

Patch Validation: Successful

Stopping RAC (/oracle/product/db/12.1.0) ... Successful

Applying patch(es) to "/oracle/product/db/12.1.0" ...
Command "/oracle/product/db/12.1.0/OPatch/opatch napply -phBaseFile /tmp/OraDB12Home1_patchList -local  -invPtrLoc /oracle/product/grid/12.1.0/oraInst.loc -oh /oracle/product/db/12.1.0 -silent -ocmrf /oracle/archivelog/patch/unconfig_GI.rsp" execution failed:
UtilSession failed: Prerequisite check "CheckActiveFilesAndExecutables" failed.

Log file Location for the failed command: /oracle/product/db/12.1.0/cfgtoollogs/opatch/opatch2015-02-24_03-26-10AM_1.log

For more details, please refer to the log file "/oracle/product/grid/12.1.0/cfgtoollogs/opatchauto/20132450/opatch_gi_2015-02-24_03-25-09_deploy.debug.log".

Apply Summary:

Following patch(es) failed to be installed:
GI Home: /oracle/product/grid/12.1.0: 19769473, 19769479, 19769480, 19872484
RAC Home: /oracle/product/db/12.1.0: 19877336, 19769479, 19769480

opatchauto failed with error code 2.


Checking the log it shows that

[Feb 24, 2015 3:26:17 AM]    Finish fuser command /sbin/fuser /oracle/product/db/12.1.0/lib/libclntsh.so.12.1 at Tue Feb 24 03:26:17 PST 2015
[Feb 24, 2015 3:26:17 AM]    Start fuser command /sbin/fuser /oracle/product/db/12.1.0/lib/libasmclntsh12.so at Tue Feb 24 03:26:17 PST 2015
[Feb 24, 2015 3:26:17 AM]    Finish fuser command /sbin/fuser /oracle/product/db/12.1.0/lib/libasmclntsh12.so at Tue Feb 24 03:26:17 PST 2015
[Feb 24, 2015 3:26:17 AM]    Following executables are active :
                             /oracle/product/db/12.1.0/lib/libclntsh.so.12.1
[Feb 24, 2015 3:26:17 AM]    Prerequisite check "CheckActiveFilesAndExecutables" failed.
                             The details are:


                             Following executables are active :
                             /oracle/product/db/12.1.0/lib/libclntsh.so.12.1
[Feb 24, 2015 3:26:17 AM]    OUI-67073:UtilSession failed: Prerequisite check "CheckActiveFilesAndExecutables" failed.
[Feb 24, 2015 3:26:17 AM]    Finishing UtilSession at Tue Feb 24 03:26:17 PST 2015
[Feb 24, 2015 3:26:17 AM]    Log file location: /oracle/product/db/12.1.0/cfgtoollogs/opatch/opatch2015-02-24_03-26-10AM_1.log
[Feb 24, 2015 3:26:17 AM]    Stack Description: java.lang.RuntimeException: Prerequisite check "CheckActiveFilesAndExecutables" failed.
[Feb 24, 2015 3:26:17 AM]    StackTrace: oracle.opatch.OPatchSessionHelper.runApplyPrereqs(OPatchSessionHelper.java:6516)
[Feb 24, 2015 3:26:17 AM]    StackTrace: oracle.opatch.opatchutil.NApply.process(NApply.java:1617)


Reason:

Some one is accessing Oracle library

Solution:

Using fuser, find who is accessing and kill it.

[root test.db.com] /oracle/home/oracle$ fuser  /oracle/product/db/12.1.0/lib/libclntsh.so.12.1
/oracle/product/db/12.1.0/lib/libclntsh.so.12.1: 112053m


[root test.db.com] /oracle/home/oracle$ ps -ef|grep 112053
oracle   112053 111991  0 Feb23 pts/0    00:00:00 sqlplus

[root test.db.com] /oracle/home/oracle$ kill -9 112053

Thursday, 27 March 2014

RMAN Connection to Auxiliary Database Fails with ORA-12641 during physical standby configuration

While connecting to Auxiliary Database for duplicating database for standby, it fails with below error



rman target sys/****@PROD1 auxiliary sys/****@STBY

Recovery Manager: Release 11.2.0.3.0 - Production on Thu Mar 27 05:12:56 2014

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

connected to target database: PROD1 (DBID=1892954352)
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04006: error from auxiliary database: ORA-12641: Authentication service failed to initialize

Reason:

SQLNET.AUTHENTICATION_SERVICES is set to "ALL" in sqlnet.ora file.

Solution:

set SQLNET.AUTHENTICATION_SERVICES to "NONE" in sqlnet.ora file on standby server and then check.

[oracle@ora-stage-sangam-d1 admin]$ rman target sys/****@PROD1 auxiliary sys/****@STBY

Recovery Manager: Release 11.2.0.3.0 - Production on Thu Mar 27 05:31:13 2014

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

connected to target database: PROD1 (DBID=1892954352)
connected to auxiliary database: PROD1 (not mounted)

RMAN>

RMAN Connection to Auxiliary Database Fails with ORA-12641 during physical standby configuration

While connecting to Auxiliary Database for duplicating database for standby, it fails with below error



rman target sys/****@PROD1 auxiliary sys/****@STBY

Recovery Manager: Release 11.2.0.3.0 - Production on Thu Mar 27 05:12:56 2014

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

connected to target database: PROD1 (DBID=1892954352)
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04006: error from auxiliary database: ORA-12641: Authentication service failed to initialize

Reason:

SQLNET.AUTHENTICATION_SERVICES is set to "ALL" in sqlnet.ora file.

Solution:

set SQLNET.AUTHENTICATION_SERVICES to "NONE" in sqlnet.ora file on standby server and then check.

[oracle@ora-stage-sangam-d1 admin]$ rman target sys/****@PROD1 auxiliary sys/****@STBY

Recovery Manager: Release 11.2.0.3.0 - Production on Thu Mar 27 05:31:13 2014

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

connected to target database: PROD1 (DBID=1892954352)
connected to auxiliary database: PROD1 (not mounted)

RMAN>

Wednesday, 19 February 2014

Error while uninstalling 11g agent.

I got below error while uninstalling an agent in silent mode.

[oracle@ora-test-a1 bin]$ ./runInstaller -deinstall -silent "REMOVE_HOMES={/oracle/product/agent11g}" -removeallfiles
Starting Oracle Universal Installer...

Checking swap space: must be greater than 500 MB.   Actual 49143 MB    Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2014-02-19_04-22-23AM. Please wait ...[oracle@inf-prod-int9-a1 bin]$ Oracle Universal Installer, Version 11.1.0.8.0 Production
Copyright (C) 1999, 2010, Oracle. All rights reserved.

OUI-10031:Inventory location cannot be empty.


Reason:

oraInventory was not updated at /etc/oraInst.loc. Update or create /etc/oraInst.loc with root user.  Entries should be like below.

cat /etc/oraInst.loc
inventory_loc=/oracle/product/11.2.0/oraInventory
inst_group=oinstall

and then run the uninstall agent command as below.

[oracle@ora-test-a1 bin]$ ./runInstaller -deinstall -silent "REMOVE_HOMES={/oracle/product/agent11g}" -removeallfiles
Starting Oracle Universal Installer...

Checking swap space: must be greater than 500 MB.   Actual 49143 MB    Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2014-02-19_04-30-37AM. Please wait ...[oracle@ora-test-a1 bin]$ Oracle Universal Installer, Version 11.1.0.8.0 Production
Copyright (C) 1999, 2010, Oracle. All rights reserved.

Starting deinstall


Deinstall in progress (Wednesday, February 19, 2014 4:30:40 AM PST)
Configuration assistant "Agent Deinstall Assistant" succeeded
Configuration assistant "Oracle Configuration Manager Deinstall" succeeded
............................................................... 100% Done.

Deinstall successful

End of install phases.(Wednesday, February 19, 2014 4:31:16 AM PST)
End of deinstallations
Please check '/oracle/product/11.2.0/oraInventory/logs/silentInstall2014-02-19_04-30-37AM.log' for more details.

Argument(s) Error... Illegal file format for composite patch.

While installing 11.2.0.3.8 composite PSU, I was getting following errors:

[oracle@ora-test-1 16902043]$ opatch apply
Oracle Interim Patch Installer version 11.2.0.3.0
Copyright (c) 2012, Oracle Corporation.  All rights reserved.

Argument(s) Error... Illegal file format for composite patch. There is no composite.xml file. Either this composite patch is not packaged properly, or you are applying a constituent individually.

Please check the arguments and try again.

OPatch failed with error code 135

Reason:

Patch apply was executed when current working directory was  "/16902043/16902043"

Solution:

We should be one directory level up while applying the patch:

cd /16902043


we need to execute "opatch apply" under //16902043 not under //16902043/16902043


Tuesday, 12 November 2013

Error starting managed server from Console :Unable to create a server socket for listening on channel "Default"

While starting the managed server from the Admin console, after nodemanager configuration, managed server was failing with status as "FAILED_to_START"

Unable to create a server socket for listening on channel "Default". The address 151.49.38.9 might be incorrect or another process is using port 18101: java.net.BindException: Cannot assign requested address.

Solution:Setup was two node cluster. I configured nodemanager and started it. but in console node manager configuration for managed server opam_server2 was showing localhost and hence it was trying to start from first node(where domain was configured) and it was failing. So update localhost with node2 hostname as below.


In Weblogic console, go to Environment -> Machines -> Configuration -> Node  Manager.

Update opam_server2 manager server with remote server host name(test2.opam.com).