Wednesday, December 21, 2016

ORA-16532: Data Guard broker configuration does not exist



ORA-16532: Data Guard broker configuration does not exist   
Step 1: Disable broker on  primary

In the Primary site disable the broker and remove the existing configuration
DGMGRL> disable configuration;
Disabled.
DGMGRL> exit

Step 2:  Find the location of the broker configuration file

[oracle@grid1vm1 ~]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.3.0 Production on Wed Mar 5 09:06:44 2014
Copyright (c) 1982, 2011, Oracle.  All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options
SQL> show parameter broker
NAME     TYPE VALUE

------------------------------------ ----------- ------------------------------

dg_broker_config_file1     string +DATA/rs1/rs1_dgbroker_config1.dat

dg_broker_config_file2     string +FRA/rs1/rs1_dgbroker_config2.dat

dg_broker_start     boolean TRUE

Step 3:   Set the dg_broker_start=false


SQL> alter system set dg_broker_start=false;

Step 4: Remove the configuration file from primary


Remove the configuration files
ASMCMD> rm +DATA/rs1/rs1_dgbroker_config1.dat

ASMCMD> rm +FRA/rs1/rs1_dgbroker_config2.dat

Step 5 :  Find the broker  configuration file in standby



In the Standby Site
SQL> show parameter broker
NAME     TYPE VALUE

------------------------------------ ----------- ------------------------------

dg_broker_config_file1     string +FRA/rs1_stb/rs1_dgbroker_config2.dat

dg_broker_config_file2     string +FRA/rs1_stb/rs1_dgbroker_config2.dat

dg_broker_start     boolean TRUE


Step 6 : Alter dg_broker_start= false in standby

SQL> alter system set dg_broker_start=false;

Step 7 :  Remove the broker configuration files in Standby


ASMCMD> rm +DATA/rs1_stb/rs1_dgbroker_config1.dat

ASMCMD> rm +FRA/rs1_stb/rs1_dgbroker_config2.dat

 Step 8 . : Recreate the Broker configuration

DGMGRL> connect /

Connected.

DGMGRL> show configuration;

ORA-16532: Data Guard broker configuration does not exist

Configuration details cannot be determined by DGMGRL


Create the new configuration

DGMGRL> create configuration rs1_dgb as primary database is rs1 connect identifier is rs1_prm;

Configuration "rs1_dgb" created with primary database "rs1"

DGMGRL> add database rs1_stb as connect identifier is rs1_stb maintained as physical;

Database "rs1_stb" added


Step 9  :  Enable the configuration  for the first time
DGMGRL> enable configuration;


Step 10 : Check the configuration file created on the respective location .

In the Primary site after enabling the configuration both files exist in their respective locations

In the Standby site after enabling the configuration both files exist in their respective locations
 

Unable To Recreate Data Guard Fast Start Failover Configuration With DGMGRL (Doc ID 454418.1)


https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=359626911642608&id=454418.1&displayIndex=1&_afrWindowMode=0&_adf.ctrl-state=ki2nqstjf_471#FIX



To BottomTo Bottom

In this Document


Symptoms

Cause

Solution

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 to 12.1.0.2 [Release 10.2 to 12.1]
Information in this document applies to any platform.
***Checked for relevance on 21-Sep-2012***
*** Reviewed for Relevance 16-Jul-2015 ***


Symptoms

-- Problem Statement:
On 10.2.0.x in Production:

When attempting to recreate a Data Guard Broker Configuration the following Error occurs when attempting
to edit the Configuration Property LogXptMode in the Primary Site :

ERROR
DGMGRL> edit database "ORCL1" set property LogXptMode='SYNC';

Error: ORA-16654: Fast-Start Failover is enabled.


-- Steps To Reproduce:
This Issue can be reproduced at will with the following Steps:

Remove the Data Guard Broker Configuration while Fast Start Failover is enabled.

1. Set up a Fast Start Failover Configuration and ensure FS_FAILOVER_STATUS is SYNCHRONIZED.

2. Place the Standby Database into READ ONLY Mode and shutdown the Standby Listener.

3. Perform a DML load on the Primary until FS_FAILOVER_STATUS becomes UNSYNCHRONIZED

4. Once the UNSYNCHRONISED State can be seen in the Primary site, kill the DMON-Process and remove the DG Broker Configuration Files.

5. DMON will restart but the FS_FAILOVER_STATUS will remain UNSYNCHRONISED.

6. At this Point the Creation of a new Data Guard Broker Configuration fails when attempting to edit the
configuration Property LogXptMode and set it to SYNC.

-- Business Impact:
The Issue has the following Business Impact:

Due to this Issue, the Data Guard Broker Configuration cannot be re-enabled and the Standby Database is
no longer protected by the Data Guard Broker and the Observer. So Fast-Start Failover is not possible at this Stage.

Cause

It appears that the Standby Protection Level of MaxAvailability is preventing the enabling of a
new Data Guard Broker Configuration. The original Configuration was removed incorrectly and is resulting
in the Failure to enable a new Configuration.

The Data Guard Physical Standby Fast Start Failover was found to be in a state of UNSYNCHRONIZED.
At this point the Data Guard Broker Configuration Files were removed from the OS Level and the DMON
Processes on each Node in the Standby Configuration were killed using OS Commands to respawn new
Processes and release the deleted Configuration Files.

Each Time the Primary Site Data Guard Broker Configuration is edited and the Property LogXptMode is set to SYNC it fails reporting Error:
ORA-16654: Fast-Start Failover is enabled.

For example:
DGMGRL> edit database "ORCL1" set property LogXptMode='SYNC';

Error: ORA-16654: Fast-Start Failover is enabled.

At this point in time in the Primary Database the Standby Database Protection Mode is set to
Maxavailability.
SQL> select DB_UNIQUE_NAME,FORCE_LOGGING,FLASHBACK_ON,LOG_MODE,OPEN_MODE,DATABASE_ROLE, GUARD_STATUS,PROTECTION_MODE,FS_FAILOVER_STATUS
from v$database

DB_UNIQUE_NAME FOR FLASHBACK_ON LOG_MODE OPEN_MODE DATABASE_ROLE
-------------- --- ------------- ------------ ---------- ----------------
GUARD_S PROTECTION_MODE FS_FAILOVER_STATUS
------- -------------------- ---------------------
orcl1 YES YES ARCHIVELOG READ WRITE PRIMARY
NONE MAXIMUM AVAILABILITY UNSYNCHRONIZED

Solution

-- To implement the solution, please execute the following steps (see Commands below)::

1. Clean up the Primary and Standby Sites.

2. Disable the Data guard Broker on each Instance

3. Remove the Data Guard Broker Configuration Files using OS-Tools.

4. Downgrade to Maximum Performance Mode on the Primary Site

5. Enable the Data Guard Broker again on all Instances

6. Recreate the Data Guard Broker Configuration

7. Raise Protection Mode back to maximum Availability using the Data Guard Broker

8. Enable Fast Start Failover again.

For example:

At the primary site:
SQL> alter system set dg_broker_start=false scope=spfile;

System altered.

SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.

SQL> ! rm $ORACLE_HOME/dbs/dr*.dat

SQL> startup nomount
ORACLE instance started.

Total System Global Area 314572800 bytes
Fixed Size 1261516 bytes
Variable Size 281018420 bytes
Database Buffers 25165824 bytes
Redo Buffers 7127040 bytes

SQL> alter system set dg_broker_start=true;

System altered.

SQL> ! ls -l $ORACLE_HOME/dbs/dr*.dat
ls: /opt/app/oracle/product/10.2.0/db_2/dbs/dr*.dat: No such file or directory

SQL> alter database mount;

Database altered.

SQL> alter database set standby database to maximize performance;

Database altered.

SQL> select DB_UNIQUE_NAME,FORCE_LOGGING,FLASHBACK_ON,LOG_MODE,OPEN_MODE,DATABASE_ROLE, GUARD_STATUS,PROTECTION_MODE,FS_FAILOVER_STATUS
from v$database

DB_UNIQUE_NAME FOR FLASHBACK_ON LOG_MODE OPEN_MODE DATABASE_ROLE
-------------- --- ------------- ------------ ---------- ----------------
GUARD_S PROTECTION_MODE FS_FAILOVER_STATUS
------- -------------------- ---------------------
orcl1 YES YES ARCHIVELOG MOUNTED PRIMARY
NONE MAXIMUM PERFORMANCE DISABLED


SQL> alter database open;

Database altered.

SQL> select DB_UNIQUE_NAME,FORCE_LOGGING,FLASHBACK_ON,LOG_MODE,OPEN_MODE,DATABASE_ROLE, GUARD_STATUS,PROTECTION_MODE,FS_FAILOVER_STATUS
from v$database

DB_UNIQUE_NAME FOR FLASHBACK_ON LOG_MODE OPEN_MODE DATABASE_ROLE
-------------- --- ------------- ------------ ---------- ----------------
GUARD_S PROTECTION_MODE FS_FAILOVER_STATUS
------- -------------------- ---------------------
orcl1 YES YES ARCHIVELOG READ WRITE PRIMARY
NONE MAXIMUM PERFORMANCE DISABLED

At the standby site:

SQL> alter system set dg_broker_start=false scope=spfile;

System altered.

SQL> shutdown immediate
ORA-01109: database not open


Database dismounted.
ORACLE instance shut down.

SQL> ! rm $ORACLE_HOME/dbs/dr*.dat

SQL> startup nomount
ORACLE instance started.

Total System Global Area 314572800 bytes
Fixed Size 1261516 bytes
Variable Size 247463988 bytes
Database Buffers 58720256 bytes
Redo Buffers 7127040 bytes

SQL> alter system set dg_broker_start=true;

System altered.

SQL> ! ls -l $ORACLE_HOME/dbs/dr*.dat
ls: /opt/app/oracle/product/10.2.0/db_2/dbs/dr*.dat: No such file or directory

SQL> alter database mount;

Database altered.

SQL> select DB_UNIQUE_NAME,FORCE_LOGGING,FLASHBACK_ON,LOG_MODE,OPEN_MODE,DATABASE_ROLE, GUARD_STATUS,PROTECTION_MODE,FS_FAILOVER_STATUS
from v$database

DB_UNIQUE_NAME FOR FLASHBACK_ON LOG_MODE OPEN_MODE DATABASE_ROLE
-------------- --- ------------- ------------ ---------- ----------------
GUARD_S PROTECTION_MODE FS_FAILOVER_STATUS
------- -------------------- ---------------------
orcl1stb YES YES ARCHIVELOG MOUNTED PHYSICAL STANDBY
NONE MAXIMUM PERFORMANCE DISABLED


From the dataguard command line:

DGMGRL> connect /
Connected.
DGMGRL> show configuration;
Error: ORA-16532: Data Guard broker configuration does not exist

Configuration details cannot be determined by DGMGRL

DGMGRL> create configuration ORCL1DG as primary database is 'ORCL1' connect identifier is
'ORCL1_ELLE';
Configuration "orcl1dg" created with primary database "ORCL1"

DGMGRL> add database 'ORCL1STB' as connect identifier is 'ORCL1_HALLE' maintained as physical;
Database "ORCL1STB" added

DGMGRL> show configuration;

Configuration
Name: orcl1dg
Enabled: NO
Protection Mode: MaxPerformance
Fast-Start Failover: DISABLED
Databases:
ORCL1 - Primary database
ORCL1STB - Physical standby database

Current status for "orcl1dg":
DISABLED

DGMGRL> enable configuration;
Enabled.

DGMGRL> show configuration;

Configuration
Name: orcl1dg
Enabled: YES
Protection Mode: MaxPerformance
Fast-Start Failover: DISABLED
Databases:
ORCL1 - Primary database
ORCL1STB - Physical standby database

Current status for "orcl1dg":
SUCCESS

DGMGRL> edit database "ORCL1" set property LogXptMode='SYNC';
Property "logxptmode" updated

DGMGRL> edit database "ORCL1STB" set property LogXptMode='SYNC';
Property "logxptmode" updated

DGMGRL> EDIT CONFIGURATION SET PROTECTION MODE AS MaxAvailability;
Succeeded.

DGMGRL> enable fast_start failover;
Enabled.

DGMGRL> show configuration;

Configuration
Name: orcl1dg
Enabled: YES
Protection Mode: MaxAvailability
Fast-Start Failover: ENABLED
Databases:
ORCL1 - Primary database
ORCL1STB - Physical standby database
- Fast-Start Failover target

Current status for "orcl1dg":
Warning: ORA-16608: one or more databases have warnings


From the Dataguard Observer node:

[oracle@elle ~]$ dgmgrl -logfile $HOME/observer.log sys/oracle@orcl1_elle "start observer" &
[1] 25249

[oracle@elle ~]$ DGMGRL for Linux: Version 10.2.0.3.0 - Production

Copyright (c) 2000, 2005, Oracle. All rights reserved.

Welcome to DGMGRL, type "help" for information.
Connected.

[oracle@elle ~]$ ps -ef | grep dgmgrl
oracle 24421 13170 0 13:34 pts/3 00:00:00 dgmgrl
oracle 25249 24675 0 13:36 pts/1 00:00:00 dgmgrl -logfile
/home/oracle/observer.log start observer
oracle 25330 24675 0 13:37 pts/1 00:00:00 grep dgmgrl


From the dataguard command line:

DGMGRL> show configuration;

Configuration
Name: orcl1dg
Enabled: YES
Protection Mode: MaxAvailability
Fast-Start Failover: ENABLED
Databases:
ORCL1 - Primary database
ORCL1STB - Physical standby database
- Fast-Start Failover target

Current status for "orcl1dg":
SUCCESS

How to Create and Enable an Oracle Data Guard Broker Configuration

https://docs.oracle.com/cd/E19421-01/820-5016/fnrfv/index.html

How to Create and Enable an Oracle Data Guard Broker Configuration

To use Oracle Data Guard with Sun Cluster Geographic Edition, you need to create an Oracle Data Guard Broker configuration.
In the following example procedure, the Oracle Data Guard Broker configuration is called mysales.com. The salesdr database is a physical copy of the sales database.
  1. Create an Oracle Data Guard Broker configuration for the primary database.
    You use the dgmgrl command to create the Oracle Data Guard Broker configuration. You need to know the name of the Oracle Data Guard Broker configuration that you want to create, the name of the primary database, and the net service name through which to connect. You will need to know these properties again, when you specify the configuration to Sun Cluster Geographic Edition.

    oracle (phys-paris-1)$ dgmgrl sys/sysdba_password@sales-svc
    DGMGRL> create configuration mysales.com as primary
    DGMGRL> database is sales connect identifier is sales-svc;
    
    If you find errors when you connect to the Oracle Data Guard Broker, check the ${ORACLE_HOME}/admin/sales/bdump/alert_prim_sid.log file. You can check that the configuration has been created by using the following command:

    oracle (phys-paris-1)$ dgmgrl sys/sysdba_password@sales-svc
    DGMGRL> show configuration;
    Configuration
      Name:                mysales.com
      Enabled:             NO
      Protection Mode:     MaxPerformance
      Fast-Start Failover: DISABLED
      Databases:
        sales   - Primary database
    
    Current status for "mysales.com":
    DISABLED
  2. Add the standby database to the Oracle Data Guard Broker configuration.
    You need to know the name of the standby database, the net service name through which to connect, and the type of standby (physical or logical).

    oracle (phys-paris-1)$ dgmgrl sys/sysdba_password@sales-svc
    DGMGRL> add database salesdr as connect identifier is 
     salesdr-svc maintained as physical;
    
  3. Configure the apply instance for the standby database.
    If the standby database is also a multi-instance Oracle RAC database, you can specify the instance on which you would prefer the transmitted archive redo logs to be applied. Before you enable the configuration, issue the following command:

    oracle$ dgmgrl sys/sysdba_password@sales-svc
    DGMGRL> edit database salesdr set property PreferredApplyInstance='salesdr1';
    
  4. To verify that the Oracle Data Guard Broker configuration is working correctly, enable the configuration.

    oracle (phys-paris-1)$ dgmgrl sys/sysdba_password@sales-svc
    DGMGRL> enable configuration;
    
    If you have successfully performed all steps, you can check the status of the configuration by using the following command:

    oracle$ dgmgrl sys/sysdba_password@sales-svc
    DGMGRL> show configuration;
    Configuration
      Name:                mysales.com
      Enabled:             YES
      Protection Mode:     MaxPerformance
      Fast-Start Failover: DISABLED
      Databases:
        sales   - Primary database
        salesdr - Physical standby database
    
    Current status for "mysales.com":
    SUCCESS
  5. Verify that the Oracle Data Guard Broker configuration can switch over.
    Before you add the Oracle Data Guard Broker configuration to Sun Cluster Geographic Edition, you need to verify that you can perform a switchover of the database from the primary to the standby and back again. If this switchover does not work, Sun Cluster Geographic Edition will not be able to perform this operation either.

    oracle (phys-paris-1)$ dgmgrl sys/sysdba_password@sales-svcDGMGRL> switchover to salesdr
    Performing switchover NOW, please wait...
    Operation requires shutdown of instance "sales1" on database "sales"
    Shutting down instance "sales1"...
    ORA-01109: database not open
    
    Database dismounted.
    ORACLE instance shut down.
    Operation requires shutdown of instance "salesdr1" on database "salesdr"
    Shutting down instance "salesdr1"...
    ORA-01109: database not open
    
    Database dismounted.
    ORACLE instance shut down.
    Operation requires startup of instance "sales1" on database "sales"
    Starting instance "sales1"...
    ORACLE instance started.
    Database mounted.
    Operation requires startup of instance "salesdr1" on database "salesdr"
    Starting instance "salesdr1"...
    ORACLE instance started.
    Database mounted.
    Switchover succeeded, new primary is "salesdr"
    
    DGMGRL switchover to sales;
    Performing switchover NOW, please wait...
    Operation requires shutdown of instance "salesdr1" on database "salesdr"
    Shutting down instance "salesdr1"...
    ORA-01109: database not open
    
    Database dismounted.
    ORACLE instance shut down.
    Operation requires shutdown of instance "sales1" on database "sales"
    Shutting down instance "sales1"...
    ORA-01109: database not open
    
    Database dismounted.
    ORACLE instance shut down.
    Operation requires startup of instance "salesdr1" on database "salesdr"
    Starting instance "salesdr1"...
    ORACLE instance started.
    Database mounted.
    Operation requires startup of instance "sales1" on database "sales"
    Starting instance "sales1"...
    ORACLE instance started.
    Database mounted.
    Switchover succeeded, new primary is "sales"

Tuesday, December 20, 2016

SOA 12C CLUSTER SETUP

http://blog.lplinux.com.ar/2016/06/15/install-oracle-soa-suite-12c-in-cluster/

SOA 12c Installation

https://www.youtube.com/watch?v=yQNgo9YKR3I
http://www.oracle.com/webfolder/technetwork/tutorials/obe/cloud/sscs/SOA12c_QSInstallation/soa-quick-start-installation.html
http://apps2fusion.com/training_demo/SOA-12c/SOA-12c-Installation-Guide.pdf
https://svgonugu.com/2014/07/04/soa-suite-12c-installation/

Monday, December 19, 2016

oracle-ebs-12-2-5-single-sign-on-using-oidoam-11g 11.1.2.3

Integrating Oracle E-Business Suite Release 12 with Oracle Access Manager 11gR2 (11.1.2) using Oracle E-Business Suite AccessGate (Doc ID 1484024.1) http://hussaindba.com/oracle-ebs-12-2-5-single-sign-on-using-oidoam-11g-part7/
http://ermanarslan.blogspot.qa/2016/06/ebs-122-road-map-and-high-level-action.html
Integrating Oracle E-Business Suite Release 12.2 with Oracle Access Manager 11gR2 (11.1.2) using Oracle E-Business Suite AccessGate (Doc ID 1576425.1)

WebLogic Server: Unable to Load Performance Pack (Doc ID 1346853.1)

WebLogic Server: Unable to Load Performance Pack (Doc ID 1346853.1)

Thursday, December 15, 2016

oam 11gR2 -oid11g -integration-steps

http://www.iamidm.com/2015/10/oam-oid-integration-steps.html

Tuesday, December 6, 2016

AUDIT VAULT AND DB FW BACKUP RESTORE STEPS

Click to add to Favorites Audit Vault Server Backup and Restore for Release 12.1.2.10.0 and Prior (Doc ID 1556200.1) To BottomTo Bottom In this Document Purpose Scope Details Backing up Audit Vault Server Restoring the Backup Special Notice on ARCHIVELOG Mode Special Notice on Hot Backup and Concurrent ILM Archive Diagnosing Failures Applies to: Oracle Audit Vault and Database Firewall - Version 12.1.0.0 and later Information in this document applies to any platform. Purpose This document describes how to create a manual backup of the Audit Vault Server installation and restoring that backup to new, replacement hardware using the Bash shell scripts from the backup_restore12.1.2.10.0.tar.gz file which is attached to this note. IMPORTANT: This version of the scripts was released on 21-MAy-2016. If you have been using the scripts attached to the previous version on this note, please upgrade your scripts immediately. Do NOT continue to use the old scripts. Note that backups taken with a previous version of the script can be restored with the new version. Note: As of Audit Vault and Database Firewall 12.2 the backup and restore feature was integrated into the appliance. You can read more about the AVDF 12.2 backup/restore in the documentation. Scope A complete Audit Vault and Database Firewall 12.1 (AVDF) configuration must exist of both Audit Vault Server(s) and Database Firewall(s). The instructions in this note only apply to the Audit Vault Server, not to the Database Firewall. Details Two types of backups are supported: hot and cold. When taking a hot backup, the Audit Vault Server functions normally. When taking a cold backup, the Audit Vault Server stops event processing during the backup operation. To enable hot backup, the Audit Vault Server’s internal Oracle database must be switched to ARCHIVELOG mode. The script archivelog.sh is provided to switch to ARCHIVELOG mode, and the script noarchivelog.sh can be used to revert Audit Vault Server back to non-ARCHIVELOG mode. The mode switch temporarily shuts down the internal database and interrupts event processing. These two scripts have to be executed as 'oracle'. The backup_restore.sh script must be executed as 'root'. NOTE: It is not necessary to switch Audit Vault Server back to non-ARCHIVELOG mode as long as regular hot backup is taken. Backing up Audit Vault Server When a backup is taken, the Audit Vault Server’s configurations and database data are copied to the backup directory. The disk space needed by the backup directory is determined by the size of the Audit Vault Server’s internal database. To find the database size, log into the server as user “oracle” and perform the following operations: $ sqlplus / as sysdba SQL> select sum (bytes)/1024/1024/1024||’ GB’ from dba_data_files It is desirable for the backup directory to be located off of the Audit Vault Server by putting it on a remote NFS export or iSCSI disk. This setup has to be manually accomplished and is outside the scope of this document. All access to the backup directory is done by user ID 503 and group ID 504. In an HA pair, backup only the primary Audit Vault Server. Backup of a secondary Audit Vault Server is not required. To create a backup, configure and run the script backup_restore.sh. The user-configurable portion of this script is wholly confined to setting script variables above the line “STOP! No user customization variables below this line”. A detailed description comes immediately above each variable. Upon successful backup, backup_restore.sh script will exit with status 0 and will output “BACKUP completed successfully” to the terminal. Restoring the Backup The restored Audit Vault Server uses all the configurations of the original server; therefore, it is not recommended to have both the restored and original Audit Vault Servers online at the same time in a single network due to IP address and database name conflicts. Follow the steps below to restore a backup: 1. Install the same version of Oracle Audit Vault and Database Firewall Server that you are attempting to restore to i.e. If you backed up from, say, 12.1.2.3.0 version and are attempting to restore that backup, please do a fresh install of 12.1.2.3.0 version of the Oracle Audit Vault and Database Firewall software. 2. Using the Web GUI of the new install, set it's date and time current. To access the Web GUI, please point your browser to https: where is the IP address of the freshly installed server. 3. If remote storage is used (in version 12.1.2.0.0 (or higher)), configure the iSCSI disks of the freshly installed AVS Server using its Web GUI or AVCLI; add disks to the appropriate ASM diskgroup to create sufficient space. Extra information is available in info.txt in the backup directory. 4. Create the backup directory at the same absolute path location (the path information is available in the backup’s info.txt file). Make sure both the backup directory and its parent directory are owned by oracle:oinstall. Stage the contents of the backup/restore archive into this directory and make them owned by oracle:oinstall. 5. Configure and run backup_restore.sh script. Make sure you set KEEP_LOGS to YES. The restore operation will complete and reboot the system automatically. 6. Once restore completes (after the automatic reboot), check the contents of the generated restore_recover.txt. Look for the lines like: ...... datafile 6 not processed because file is offline datafile 7 not processed because file is offline ...... 7. If you do not see the above lines, you can skip to step 8. Log on through RMAN and connect target. Do RMAN> connect target / If password is set during backup, set the decryption password. RMAN> set decryption identified by ''; Do RMAN> restore datafile 6,7; where the numbers are from the list we found from step 6. 8. Update /var/lib/oracle/dbfw/av/conf/bootstrap.prop. Make sure both HOST IPs of the connect strings are pointing to the original Audit Vault and Database Firewall Server i.e. use the IP address of the original Audit Vault and Database Server for both places. 9. If NFS ILM Archive locations were used, manually remount those NFS locations using AVCLI. When restoring a backup taken on an HA primary Audit Vault Server, the restored HA status is switched to “standalone”. Special Notice on ARCHIVELOG Mode In order to perform a hot backup, the Audit Vault Server’s internal database must be in ARCHIVELOG mode. While in ARCHIVELOG mode, old database redo logs are saved until each backup operation; this requires additional disk space in /var/lib/oracle (for pre-12.1.2.0.0) and +RECOVERY (for 12.1.2.0.0 and higher). The disk space requirement is proportional to the amount of incoming events between backups. The default size of 10GB should be enough when regular backups (whether full or incremental) are taken. Special Notice on Hot Backup and Concurrent ILM Archive Part of the ILM archive job deletes transferred datafile(s), and tablespace with deleted datafiles are marked not-to-be-backup (i.e. v$tablespace.included_in_database_backup). However, when an ILM archive job (which must be user initiated) runs concurrently with a backup (via backup_restore.sh), there is a race between backup_restore.sh reading a datafile and ILM deleting that datafile. If ILM deletes the datafile while backup_restore.sh is still reading, an RMAN error of missing datafile is reported by backup_restore.sh. The workaround is to re-run backup_restore.sh when the ILM job finishes. This issue is not applicable to cold backup because the Audit Vault Server’s internal database is shutdown during a cold backup which prevents users from initiating an ILM archive job. Diagnosing Failures During the execution of the script, logs of the script activities are written to the location specified by the TMP_DIR variable. It may be necessary to examine these logs to determine the cause of script failure (e.g. RMAN IO error in the log indicates disk access failure such as out of disk space). Known issues: #1 The restore script does not work for Cold incremental 1 backup. Please do not use the backup_restore.sh to get Cold incremental 1 backups for they will not be usable.

Thursday, December 1, 2016

stating weblogc managed server from the console

Inorder to start the managed server, from the console do the following 1. Start the node manager, it will throw and error but 2. It will create nodemanager.properties 3. Change the StartScriptEnabled=true in nodemanager.properties 4. Star the node manager again . 5. login to console and start the managed server $ cat /u01pa/MW_Home/wlserver_10.3/common/nodemanager/nodemanager.properties | grep true AuthenticationEnabled=true DomainsFileEnabled=true NativeVersionEnabled=true LogToStderr=true SecureListener=true LogAppend=true StartScriptEnabled=true

Oracle WebLogic Server 12c: Configuring and Using Node Manager

http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/wls/12c/10-NodeMgr--4472/nodemgr.htm http://biemond.blogspot.qa/2011/04/easy-wy-to-start-your-weblogic-servers.html Oracle WebLogic Server 12c: Configuring and Using Node Manager Purpose This tutorial shows how to configure and use the Oracle WebLogic Server 12c Java-based Node Manager. Time to Complete Approximately 1 hour Overview In a production environment, WebLogic Server instances are often distributed across multiple domains, machines, and geographic locations. Node Manager is a WebLogic Server utility that enables you to start, shut down, and restart the administration server and managed servers from a remote location. Although Node Manager is not required, it is recommended if your WebLogic Server environment hosts applications with high availability requirements. A Node Manager process is not associated with a specific WebLogic domain, but with a particular machine. You can use the same Node Manager process to control server instances from any WebLogic Server domain, as long as those server instances reside on the same machine as the Node Manager process. This tutorial covers configuring and starting the Java-based Node Manager and using it to control Oracle WebLogic Server 12c (12.1.1) managed servers. Software Requirements The following is a list of software requirements: Oracle WebLogic Server 12c (12.1.1) Prerequisites Before starting this tutorial, you should have completed the Oracle by Example tutorials titled Oracle WebLogic Server 12c: Installing WebLogic Server and Creating a Domain, Oracle WebLogic Server 12c: Configuring Managed Servers, and Oracle WebLogic Server 12c: Creating and Configuring Machines. Inspecting the Current Machine Configuration To check the configuration of the machines created in the earlier tutorial, perform the following steps: 1. If the administration server of the domain is not already running, it must be started. To start it, in a Terminal window, navigate to the domain directory, and enter the command: $ ./startWebLogic.sh Screenshot for Step When prompted for a username and password, enter the credentials of the domain administrator. 2. After the administration server is up and running, access the WebLogic Server administration console. Open a web browser and enter the URL: http://hostname:port/console In this tutorial, that is: http://host01.example.com:8001/console Note: Use the host name of your host. Also, if you used a different port number for the administration server, use that port instead. On the Welcome screen, log in using the username and password entered to start the administration server. Screenshot for Step 3. If any of the managed servers (dizzy1, dizzy2, dizzy3) are running, shut them down. 4. Check the configuration of the machines created in the tutorial titled Oracle WebLogic Server 12c: Creating and Configuring Machines. Under Domain Structure, expand Environment (by clicking the + next to it). Then click Machines. Screenshot for Step 5. In the Machines table, click dizzyMachine1. Screenshot for Step 6. Under Settings for dizzyMachine1, click the Configuration tab and the Node Manager subtab. Screenshot for Step 7. Here you can see the settings for the Node Manager for this machine. It has the Type set to Plain (which means the Java-based Node Manager that does not use SSL), the Listen Address set to host01.example.com , and the Listen Port set to 5556. Screenshot for Step 8. Also check the Node Manager settings for dizzyMachine2. Back under the Domain Structure, under Environment, click Machines. In the Machines table, click dizzyMachine2. Under Settings for dizzyMachine2, click the Configuration tab and the Node Manager subtab. Here you can see the settings for the Node Manager for dizzyMachine2. It has the same settings as the Node Manager for dizzyMachine1, except the Listen Address is set to host02.example.com and the Listen Port is set to 5557. Screenshot for Step Configuring Node Manager To create a new Node Manager home directory on a machine and then configure its settings, perform the following steps: 1. Open a new Terminal on host01, and navigate to the installation directory, . In this tutorial it is: /u01/app/oracle/Middleware. 2. Create a new directory /user_projects/nodemanager/dizzyMachine1. Screenshot for Step 3. Copy the following file to the dizzyMachine1 directory: /wlserver_12.1/server/bin/startNodeManager.sh. Screenshot for Step 4. Edit the file /user_projects/nodemanager/dizzyMachine1/startNodeManager.sh. 5. Set the NODEMGR_HOME variable to the current path. In this tutorial, it is /user_projects/nodemanager/dizzyMachine1. Then save your changes. Screenshot for Step 6. Create a new file /user_projects/nodemanager/dizzyMachine1/nodemanager.properties and edit it. 7. Add the following three lines to the new file: ListenAddress=host01.example.com ListenPort=5556 SecureListener=false Then save your changes. Screenshot for Step 8. Access the second machine, host02. You will set up node manager here as well, this time for dizzyMachine2: Create a new directory /user_projects/nodemanager/dizzyMachine2, and copy the startNodeManager.sh script into this location. Edit the copied script to set the NODEMGR_HOME variable to the current path. In this tutorial, it is /user_projects/nodemanager/dizzyMachine2. Save the file. Create a nodemanager.properties file once again, but this time enter the listen address and port number for dizzyMachine2: ListenAddress=host02.example.com ListenPort=5557 SecureListener=false Save this file. Screenshot for Step Enrolling Computers with a Domain To enroll a computer with a domain, so that the Node Manager on that computer will accept requests from the domain, perform the following steps: 1. Access host01. In a Terminal window navigate to /wlserver_12.1/server/bin. Run the setWLSEnv.sh script to set up the environment needed for WLST as follows: $ source setWLSEnv.sh Screenshot for Step 2. Open WLST in interactive mode by entering the following command in the Terminal window: java weblogic.WLST Screenshot for Step 3. At the WLST prompt, enter the following command to connect to the running administration server: wls:/offline> connect('', '', 't3://:') Replace the sample argument values with those that match your domain environment. In this tutorial, the command is: wls:/offline> connect('weblogic', 'Welcome1', 't3://host01.example.com:8001') Screenshot for Step 4. Run the nmEnroll() command. This command enrolls the computer on which WLST is running with the domain of the administration server to which WLST is connected. What "enrolling" means is the command downloads two files from the administration server to this computer: nm_password.properties and SerializedSystemIni.dat. The Node Manager "secret file," nm_password.properties, contains the encrypted username and password used by the adminstration server to authenticate itself to the Node Manager process. This file is placed in the domain directory under /config/nodemanager/. The file used for encryption and decryption, SerializedSystemIni.dat, is placed in the domain directory under /security/. In addition, the nmEnroll() command creates or updates the nodemanager.domains file found in the Node Manager home directory. It adds the current domain to the list of domains that this Node Manager is allowed to manage. The nmEnroll() command has two arguments: The domain home directory on this computer The Node Manager home directory on this computer In this tutorial, the command is: nmEnroll('/u01/app/oracle/Middleware/user_projects/domains/dizzyworld', '/u01/app/oracle/Middleware/user_projects/nodemanager/dizzyMachine1') Note: Be sure to put the right path to your domain and to your Node Manager when using the command. Screenshot for Step 5. Exit WLST by entering the following command at the prompt: exit() Screenshot for Step 6. Access host02 and repeat these steps to run nmEnroll() for the dizzyMachine2 Node Manager home directory: nmEnroll('/u01/app/oracle/Middleware/user_projects/domains/dizzyworld', '/u01/app/oracle/Middleware/user_projects/nodemanager/dizzyMachine2') Starting Node Manager To start Node Manager, perform the following steps: 1. On host01, navigate to /user_projects/nodemanager/dizzyMachine1 and enter: ./startNodeManager.sh Screenshot for Step Notice that Node Manager starts for dizzyMachine1. Screenshot for Step 2. On host02, navigate to /user_projects/nodemanager/dizzyMachine2 and enter: ./startNodeManager.sh Starting Servers with Node Manager and the Administration Console To start the managed servers from the console, perform the following steps: 1. Access the WebLogic Server administration console again. In the Domain Structure section, expand Environment and click Servers. Screenshot for Step 2. Click the Control tab. Screenshot for Step 3. Select the check boxes for all of the managed servers (dizzy1, dizzy2, and dizzy3). Then click the Start button. Screenshot for Step 4. When prompted for confirmation to start the three servers, click Yes Screenshot for Step Screenshot for Step 5. Click the refresh icon to periodically refresh the Servers table. Screenshot for Step 6. After a few minutes, verify that each server's State is "Running." Screenshot for Step Summary In this tutorial, you learned how to: Configure Node Manager communication settings in a domain Configure and start a Node Manager Enroll a domain with a Node Manager Start servers with Node Manager Resources For documentation on Oracle WebLogic Server 12c, visit the Documentation Library. For more information on configuring machines, see the Create and configure machines section of the Administration Console Online Help. For more information on configuring and using Node Manager, see the Node Manager Administrator's Guide. To learn more about Oracle WebLogic Server, refer to additional OBEs in the OLL website. Credits Author: TJ Palazzolo Contributor: Bill Bell

StartWebLogic.cmd Shuts Down after Entering Username with the Error: "Server is running in Production Mode and Native Library (terminalio) to read the password securely from commandline is not found

StartWebLogic.cmd Shuts Down after Entering Username with the Error: "Server is running in Production Mode and Native Library (terminalio) to read the password securely from commandline is not found." (Doc ID 1354736.1) To BottomTo Bottom In this Document Symptoms Cause Solution References Applies to: Primavera Contract Management - Version 13.0 and later Primavera Unifier - Version 9.12 and later Information in this document applies to any platform. Symptoms After creating the WebLogic Domain for the Primavera Application, installing the application, and then restarting WebLogic, the StartWebLogic.cmd or StartWebLogic.sh file shuts down or closes after typing a username and pressing the ENTER key. The following error is listed in the StartWebLogic command prompt window or terminal window prior to the shutdown completing: Server is running in Production Mode and Native Library (terminalio) to read the password securely from commandline is not found. Cause There are two possible causes: The terminalio.dll file is missing from the default location: C:\bea\middleware\wlserver_10.3\server\native\win\32 The terminalio.dll filing is being renamed to terminalio.dll.bak when the StartWeblogic.cmd or StartWeblogic.sh file is started. This known issue has been reported to Oracle and is documented in Bug 8002166. Solution To resolve this issue, open the StartWebLogic.cmd or StartWebLogic.sh file with Notepad or Text Editor and do the following: Located towards the bottom of the file are the following lines: if "%WLS_REDIRECT_LOG%"=="" ( echo Starting WLS with line: echo %JAVA_HOME%\bin\java %JAVA_VM% %MEM_ARGS% -Dweblogic.Name=%SERVER_NAME% -Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy %JAVA_OPTIONS% %PROXY_SETTINGS% %SERVER_CLASS% %JAVA_HOME%\bin\java %JAVA_VM% %MEM_ARGS% -Dweblogic.Name=%SERVER_NAME% -Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy %JAVA_OPTIONS% %PROXY_SETTINGS% %SERVER_CLASS% ) else ( echo Redirecting output from WLS window to %WLS_REDIRECT_LOG% %JAVA_HOME%\bin\java %JAVA_VM% %MEM_ARGS% -Dweblogic.Name=%SERVER_NAME% -Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy %JAVA_OPTIONS% %PROXY_SETTINGS% %SERVER_CLASS% >"%WLS_REDIRECT_LOG%" 2>&1 ) Change them by including the following line directly before %JAVA_OPTIONS%: -Dweblogic.management.allowPasswordEcho=true The changed information should now appear as: if "%WLS_REDIRECT_LOG%"=="" ( echo Starting WLS with line: echo %JAVA_HOME%\bin\java %JAVA_VM% %MEM_ARGS% -Dweblogic.Name=%SERVER_NAME% -Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy -Dweblogic.management.allowPasswordEcho=true %JAVA_OPTIONS% %PROXY_SETTINGS% %SERVER_CLASS% %JAVA_HOME%\bin\java %JAVA_VM% %MEM_ARGS% -Dweblogic.Name=%SERVER_NAME% -Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy -Dweblogic.management.allowPasswordEcho=true %JAVA_OPTIONS% %PROXY_SETTINGS% %SERVER_CLASS% ) else ( echo Redirecting output from WLS window to %WLS_REDIRECT_LOG% %JAVA_HOME%\bin\java %JAVA_VM% %MEM_ARGS% -Dweblogic.Name=%SERVER_NAME% -Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy -Dweblogic.management.allowPasswordEcho=true %JAVA_OPTIONS% %PROXY_SETTINGS% %SERVER_CLASS% >"%WLS_REDIRECT_LOG%" 2>&1 ) Be sure to leave a space before and after the line that was just added. Save the changes and then restart StartWebLogic.cmd or StartWebLogic.sh. Was this document helpful? Yes No Document Details Email link to this documentOpen document in new windowPrintable Page Type: Status: Last Major Update: Last Update: PROBLEM PUBLISHED Jul 7, 2015 Jul 7, 2015 Related Products Primavera Contract Management Primavera Unifier Information Centers Information Center: Primavera Contract Management v13 [1091924.2] Document References No References available for this document. Recently Viewed StartWebLogic.cmd Shuts Down after Entering Username with the Error: "Server is running in Production Mode and Native Library (terminalio) to read the password securely from commandline is not found." [1354736.1] OAM 11gR2 : configuresecuritystore.py Fails To Run While Installing 11gR2 On Solaris SPARC Platform [1514647.1] Failure To Create Security Store: configureSecurityStore.py Generates Error ORA-01017: invalid username/password; logon denied [1941328.1] Oracle E-Business Suite Software Development Kit for Java (includes AppsDataSource, Java Authentication and Authorization Service, session management) Readme - Patch 13882058 [974949.1] R12: "ORA-01017: invalid username/password; logon denied" Error Message When Attempting to Create a JDBC Data Source [1099562.1] Show More Didn't find what you are looking for?