This exercise is to move everything from old OCR/VOTING diskgroup OCR_VOTE to a new diskgroup OCR_VOTE2 in 11.2.0.4.
Subscribe to get access
Read more of this content when you subscribe today.
It is recommended to put OCR, Voting File and ASM SPILE onto a dedicated diskgroup.
This exercise is to move everything from old OCR/VOTING diskgroup OCR_VOTE to a new diskgroup OCR_VOTE2 in 11.2.0.4.
Read more of this content when you subscribe today.
After the DB user password is changed by DBA, or after the ORMB schema is refreshed from other environment and need keep the password of old one. The DB user password needs to be changed as per Oracle Doc.
For example, CISADM_TEST was refreshed from CISADM_PROD. In ORMB database, the password is still the one of CISADM_PROD.
Read more of this content when you subscribe today.
In Unicode AL32UTF8, special characters, invalid characters might cause errors like “ORA-39346: data loss in character set conversion”.
When importing a schema exported from one 12cR1 AL32UTF8 database to another database with same AL32UTF8 characterset, this ORA -error was generated :
ORA-39346: data loss in character set conversion for object SCHEMA_EXPORT/TABLE/COMMENT
The error message clearly shows the problem data is from “SCHEMA_EXPORT/TABLE/COMMENT”.
Using MDU tool ( Database Migration Assistant for Unicode ) to scan database Dictionary Objects, we can see the problem data is from SYS.COM$.

Read more of this content when you subscribe today.
Using MDU tool ( Database Migration Assistant for Unicode ) to scan database Dictionary Objects again, we can see all green including SYS.COM$.
Do another export and import again, everything works fine.
Oracle DBMS Scheduler is the easiest and cost saving way for ORMB Batch Scheduling.
The Patch id is 23639775, which can be downloaded from Oracle support.
This patch is supposed to be installed on to ORMB application server. But we zip it and ship onto a Windows server for installation.
$ unzip Oracle_Scheduler_Integration.zip Archive: Oracle_Scheduler_Integration.zip inflating: Getting Started Guide ORMB Batch Scheduling.pdf inflating: ORACLE_DBMS_SCHEDULER_SETUP_LINUX.pdf inflating: ORMB_Integration_Installer/lastDayPrevMonthJobs.properties inflating: ORMB_Integration_Installer/readme.txt inflating: ORMB_Integration_Installer/setup.sh inflating: ORMB_Integration_Installer/sql/oem_ouaf_package.sql inflating: ORMB_Integration_Installer/sql/ouaf_batch_package.sql inflating: ORMB_Integration_Installer/sql/setup.sql inflating: ORMB_Integration_Installer/sql/user_cisadm_setup.sql inflating: ORMB_Integration_Installer/sql/user_schadm_NEW_I.sql inflating: ORMB_Integration_Installer/sql/user_schadm_NEW_S.sql inflating: ORMB_Integration_Installer/sql/user_schadm_setup_NEW.sql inflating: ORMB_Integration_Installer/sql/user_schadm_setup_OEM_N.sql inflating: ORMB_Integration_Installer/sql/user_schadm_setup_OEM_Y.sql inflating: ORMB_Integration_Installer/sql/user_schadm_setup_UPD.sql extracting: ORMB_Integration_Installer/sql/user_schadm_UPD_I.sql extracting: ORMB_Integration_Installer/sql/user_schadm_UPD_S.sql $ cd ORMB_Integration_Installer oracle@racnode1:/tmp/ORMB_Integration_Installer$ chmod 777 setup.sh oracle@racnode1:/tmp/ORMB_Integration_Installer$ sqlplus / as sysdba SQL*Plus: Release 12.1.0.2.0 Production on Thu Mar 16 10:23:42 2017 Copyright (c) 1982, 2014, Oracle. All rights reserved. Connected to: Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP, Advanced Analytics and Real Application Testing options SQL> alter session set container=ormbpdb; Session altered. SQL> show user USER is "SYS" SQL> @?/rdbms/admin/userlock.sql; Package dropped. Package created. Package body created. Synonym created. Grant succeeded. SQL> grant execute,debug on user_lock to cisadm; Grant succeeded. oracle@racnode1:/tmp/ORMB_Integration_Installer$ ls -ltr total 16 -rwxrwxrwx 1 oracle oinstall 417 Mar 14 16:10 setup.sh -rw-r--r-- 1 oracle oinstall 3485 Mar 14 16:10 readme.txt -rw-r--r-- 1 oracle oinstall 112 Mar 14 16:10 lastDayPrevMonthJobs.properties drwxr-xr-x 2 oracle oinstall 4096 Mar 16 10:20 sql oracle@racnode1:/tmp/ORMB_Integration_Installer$ ./setup.sh OUAF DBMS Scheduler Setup (4.2.x, 4.3.x) ======================================== NOTES: 1. Package USER_LOCK must be installed before running this script. That can typically be done by executing @?/rdbms/admin/userlock.sql 2. The schema owner (e.g. CISADM) must have "create user" permission. Hit enter to start Enter database service (SID) name: ORMB Enter schema owner [CISADM]: cisadm Enter password for user cisadm: xxxxxx Connecting to cisadm@ORMB ... Validating user cisadm Checking USER_LOCK package Enter scheduler user name [SCHADM]: schadm User SCHADM does not exist and will be created Enter password for user SCHADM: Confirm password for user SCHADM: xxxxxx Enter default tablespace [CISTS_01]: CISADM Enter temp tablespace [TEMP]: Creating user SCHADM Connecting to SCHADM@ORMB ... The email server, recipient and sender addresses are required for email notifications when threads end in error and the thread_notifications option is in effect. These values can be set here or the defaults can be accepted and then modified by connecting to user SCHADM and: a) running statement "DBMS_SCHEDULER.set_scheduler_attribute(...)" to change the email server and b) editing scheduler job OUAF_NOTIFY and changing its email notification settings. Enter email server name [mailserver.company.com]: smtp.wordpress.com Enter email recipient address [foo.bar@company.com]: infor@dbalifeeasy.com Enter email sender address [do-not-reply@company.com]: schadm@dbalifeeasy.com Use OEM_NOTIFY for thread errors (Y/N)? [N]: Y Job OEM_NOTIFY will be used for thread error notifications OUAF DBMS Scheduler setup completed
We will follow the following steps to achieve this :
Read more of this content when you subscribe today.
Setting “ADMIN_RESTRICTIONS_listener_name=on” disables the runtime
modification of parameters in listener.ora.
Got error message “TNS-12508: TNS:listener could not resolve the COMMAND given” when trying to switch off listener log.
LSNRCTL> set log_status off Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=racnode1)(PORT=1521))) TNS-12508: TNS:listener could not resolve the COMMAND given LSNRCTL>
Read more of this content when you subscribe today.