Eg.
BEGIN DBMS_APPLY_ADM.SET_DML_HANDLER(
object_name => '
object_type => 'TABLE',
operation_name => 'INSERT',
error_handler => false,
user_procedure => NULL ,
apply_database_link => NULL,
apply_name => NULL);
END;
/
Thursday, December 11, 2008
Unset streams DML handler
To unset DML handler in a streams environment, simply point "user_procedure" to NULL.
Eg.
BEGIN DBMS_APPLY_ADM.SET_DML_HANDLER(
object_name => '',
object_type => 'TABLE',
operation_name => 'INSERT',
error_handler => false,
user_procedure => NULL ,
apply_database_link => NULL,
apply_name => NULL);
END;
/
Eg.
BEGIN DBMS_APPLY_ADM.SET_DML_HANDLER(
object_name => '
object_type => 'TABLE',
operation_name => 'INSERT',
error_handler => false,
user_procedure => NULL ,
apply_database_link => NULL,
apply_name => NULL);
END;
/
Monday, December 1, 2008
How to re-synchronize the streams replicated objects online
Refer to My Oracle Support(Metalink), Note:749036.1 publish on 23-NOV-2008.
In case some reader couldn't access Metalink, refer below.
Applies to: Oracle Server - Enterprise Edition - Version: 10.2 to 11.1
Information in this document applies to any platform.
Goal: In-cases we need to re-synchronize the data between the replicating sites, like for example in cases of errors like ORA-01403 / ORA-1422 reported by the apply process because data is out of sync, and resynchronizing manually is not feasible.
Here are the steps we need to do to re-synchronize the data between the source and target site in the streams environment, without the need to stop the activity on the replicated objects on the source site. .
Solution
In here we assume that we have one SOURCE and one TARGET and streams replication is configured between them. For more complicated environments, some modifications/additions may be needed on these steps.
Here is what we need to do:
1. Stop the capture and apply processes:
-- Stop the capture process:
exec dbms_capture_adm.stop_capture('');
-- Make sure its stopped:
select capture_name, status from dba_capture;
-- Stop the apply process:
exec dbms_apply_adm.stop_apply('');
-- Make sure its stopped:
select apply_name, status from dba_apply;
2. Purge the Capture and apply queue tables:
- As we will re-synch; The messages in both source queue that has not been propagated yet, and messages in the apply queue that has not been applied yet, can both be purged.
You can do this step of purging the capture and apply queue if and only if you are doing complete resync of all the streams replication objects. If you are doing synchronization for some of the objects, then do not attempt to purge any of the queues or the other objects will get out of sync
- There will be no problem if you skipped that step, the apply process will still bypass all those messages, we just do that incase we got alot of messages that may take long time to be propagated and skipped by the apply process.
-- Stop the propagation:
exec dbms_propagation_adm.stop_propagation('');
select propagation_name, status from dba_propagation;
-- To purge perform the following for both the capture and apply queue tables:
DECLARE
options dbms_aqadm.aq$_purge_options_t;
BEGIN
options.delivery_mode:=DBMS_AQADM.BUFFERED; DBMS_AQADM.PURGE_QUEUE_TABLE('',NULL,options);
END;
/
-- check that the messages has been successfully pruged for capture and apply queue:
SELECT QUEUE_SCHEMA, QUEUE_NAME, (NUM_MSGS - SPILL_MSGS) MEM_MSG, SPILL_MSGS, NUM_MSGS FROM V$BUFFERED_QUEUES where queue_name='';
-- Start the propagation again:
exec dbms_propagation_adm.start_propagation(''); select propagation_name, status from dba_propagation;
3. Export the source schema:
-- For example we are replicating schema "MARS", so we should do the following:
exp system/oracle owner=mars file=mars.dump log=mars.log object_consistent=Y
*Object_consistent must be set to Y, so the imported data would be consistent with the source.
4) Delete the apply errors:
As we will re-synchronize, we can delete the errors that are in the error_queue of the apply process.
To do so, we can execute either DBMS_APPLY_ADM.DELETE_ERROR or DBMS_APPLY_ADM.DELETE_ALL_ERRORS at the apply site.
You need to make sure that you are not deleting any needed transaction, specially if you are not synchronizing all the replicated for that apply process. If you are synchronizing all the data you can execute directly DBMS_APPLY_ADM.DELETE_ALL_ERRORS.
-- Check the errors in the error queue:
select apply_name, LOCAL_TRANSACTION_ID, ERROR_MESSAGE from dba_apply_error;
-- To delete specific transaction:
exec DBMS_APPLY_ADM.DELETE_ERROR('');
-- To delete all errors:
exec DBMS_APPLY_ADM.DELETE_ALL_ERRORS('');
If you need to check the contents of the transactions before deleting check the procedures in documentation:
> Oracle® Streams Concepts and Administration 10g Release 2 (10.2) Part Number B14229-04 > 22 Monitoring Streams Apply Processes
> Displaying Detailed Information About Apply Errors
5. Import the source schema to target:
imp system/oracle file=mars.dump full=y ignore=y STREAMS_INSTANTIATION=Y
When doing STREAMS_INSTANTIATION=Y and having the export done with object_consistent=Y, the instantiation SCN for the apply will be modified to the SCN at the time the export was taken, and this will insure that data at the target is consistent with data at the source.
In the example above of exp/imp we are assuming that we are replicating schema MARS, and we are trying to synchronize it, but we may also exp/imp specific tables, we do not have to synchronize the whole schema when we are doing schema level streams.
Note:
- After doing the import, we are now sure that the data is now consistent, and the apply process will only apply changes starting from the SCN after the time of the export.
- If the exp/imp will be done using datapump, then we will not need to set any parameters, as the imported objects will be automatically imported with the SCN of the source at point in time where the export was taken, as long as there is an existing apply process on the apply site.
6. Start capture and apply:
-- Start the apply process:
exec dbms_apply_adm.start_apply('');
-- Make sure apply is started
select apply_name, status from dba_apply;
-- Start the capture process:
exec dbms_capture_adm.start_capture('');
-- Make sure capture is started
select capture_name, status from dba_capture;
In case some reader couldn't access Metalink, refer below.
Applies to: Oracle Server - Enterprise Edition - Version: 10.2 to 11.1
Information in this document applies to any platform.
Goal: In-cases we need to re-synchronize the data between the replicating sites, like for example in cases of errors like ORA-01403 / ORA-1422 reported by the apply process because data is out of sync, and resynchronizing manually is not feasible.
Here are the steps we need to do to re-synchronize the data between the source and target site in the streams environment, without the need to stop the activity on the replicated objects on the source site. .
Solution
In here we assume that we have one SOURCE and one TARGET and streams replication is configured between them. For more complicated environments, some modifications/additions may be needed on these steps.
Here is what we need to do:
1. Stop the capture and apply processes:
-- Stop the capture process:
exec dbms_capture_adm.stop_capture('
-- Make sure its stopped:
select capture_name, status from dba_capture;
-- Stop the apply process:
exec dbms_apply_adm.stop_apply('
-- Make sure its stopped:
select apply_name, status from dba_apply;
2. Purge the Capture and apply queue tables:
- As we will re-synch; The messages in both source queue that has not been propagated yet, and messages in the apply queue that has not been applied yet, can both be purged.
You can do this step of purging the capture and apply queue if and only if you are doing complete resync of all the streams replication objects. If you are doing synchronization for some of the objects, then do not attempt to purge any of the queues or the other objects will get out of sync
- There will be no problem if you skipped that step, the apply process will still bypass all those messages, we just do that incase we got alot of messages that may take long time to be propagated and skipped by the apply process.
-- Stop the propagation:
exec dbms_propagation_adm.stop_propagation('
select propagation_name, status from dba_propagation;
-- To purge perform the following for both the capture and apply queue tables:
DECLARE
options dbms_aqadm.aq$_purge_options_t;
BEGIN
options.delivery_mode:=DBMS_AQADM.BUFFERED; DBMS_AQADM.PURGE_QUEUE_TABLE('
END;
/
-- check that the messages has been successfully pruged for capture and apply queue:
SELECT QUEUE_SCHEMA, QUEUE_NAME, (NUM_MSGS - SPILL_MSGS) MEM_MSG, SPILL_MSGS, NUM_MSGS FROM V$BUFFERED_QUEUES where queue_name='
-- Start the propagation again:
exec dbms_propagation_adm.start_propagation('
3. Export the source schema:
-- For example we are replicating schema "MARS", so we should do the following:
exp system/oracle owner=mars file=mars.dump log=mars.log object_consistent=Y
*Object_consistent must be set to Y, so the imported data would be consistent with the source.
4) Delete the apply errors:
As we will re-synchronize, we can delete the errors that are in the error_queue of the apply process.
To do so, we can execute either DBMS_APPLY_ADM.DELETE_ERROR or DBMS_APPLY_ADM.DELETE_ALL_ERRORS at the apply site.
You need to make sure that you are not deleting any needed transaction, specially if you are not synchronizing all the replicated for that apply process. If you are synchronizing all the data you can execute directly DBMS_APPLY_ADM.DELETE_ALL_ERRORS.
-- Check the errors in the error queue:
select apply_name, LOCAL_TRANSACTION_ID, ERROR_MESSAGE from dba_apply_error;
-- To delete specific transaction:
exec DBMS_APPLY_ADM.DELETE_ERROR('
-- To delete all errors:
exec DBMS_APPLY_ADM.DELETE_ALL_ERRORS('
If you need to check the contents of the transactions before deleting check the procedures in documentation:
> Oracle® Streams Concepts and Administration 10g Release 2 (10.2) Part Number B14229-04 > 22 Monitoring Streams Apply Processes
> Displaying Detailed Information About Apply Errors
5. Import the source schema to target:
imp system/oracle file=mars.dump full=y ignore=y STREAMS_INSTANTIATION=Y
When doing STREAMS_INSTANTIATION=Y and having the export done with object_consistent=Y, the instantiation SCN for the apply will be modified to the SCN at the time the export was taken, and this will insure that data at the target is consistent with data at the source.
In the example above of exp/imp we are assuming that we are replicating schema MARS, and we are trying to synchronize it, but we may also exp/imp specific tables, we do not have to synchronize the whole schema when we are doing schema level streams.
Note:
- After doing the import, we are now sure that the data is now consistent, and the apply process will only apply changes starting from the SCN after the time of the export.
- If the exp/imp will be done using datapump, then we will not need to set any parameters, as the imported objects will be automatically imported with the SCN of the source at point in time where the export was taken, as long as there is an existing apply process on the apply site.
6. Start capture and apply:
-- Start the apply process:
exec dbms_apply_adm.start_apply('
-- Make sure apply is started
select apply_name, status from dba_apply;
-- Start the capture process:
exec dbms_capture_adm.start_capture('
-- Make sure capture is started
select capture_name, status from dba_capture;
Monday, November 24, 2008
sqlplus give error /usr/lib/hpux64/dld.so: Unable to find library 'libclntsh.so.10.1'
When other user in HP-UX run sqlplus and system give following error:
/usr/lib/hpux64/dld.so: Unable to find library 'libclntsh.so.10.1'
Solution:chmod -R 755 $ORACLE_HOME
/usr/lib/hpux64/dld.so: Unable to find library 'libclntsh.so.10.1'
Solution:chmod -R 755 $ORACLE_HOME
Wednesday, November 19, 2008
Oracle 11g New Feature - Checking DB alert log
Checking alert log is no longer necessary to be done from OS level.
You can query v$diag_info view for alert information.
You can query v$diag_info view for alert information.
Wednesday, November 12, 2008
Drop dbcontrol repository
emca -config dbcontrol db -repos drop -silent -PORT -SERVICE_NAME -SYS_PWD -SID -DBSNMP_PWD -SYSMAN_PWD -DBCONTROL_HTTP_PORT -AGENT_PORT -RMI_PORT -JMS_PORT
Eg.
emca -config dbcontrol db -repos drop -silent -PORT 1521 -SERVICE_NAME MESTEST -SYS_PWD SYS -SID MESTEST -DBSNMP_PWD dbsnmp -SYSMAN_PWD sysman -DBCONTROL_HTTP_PORT 1158 -AGENT_PORT 3938 -RMI_PORT 5521 -JMS_PORT 5541
Eg.
emca -config dbcontrol db -repos drop -silent -PORT 1521 -SERVICE_NAME MESTEST -SYS_PWD SYS -SID MESTEST -DBSNMP_PWD dbsnmp -SYSMAN_PWD sysman -DBCONTROL_HTTP_PORT 1158 -AGENT_PORT 3938 -RMI_PORT 5521 -JMS_PORT 5541
Create new repository to enable dbcontrol in Oracle 10.2
emca -config dbcontrol db -repos create -silent -PORT -SERVICE_NAME -SYS_PWD -SID -DBSNMP_PWD -SYSMAN_PWD -DBCONTROL_HTTP_PORT -AGENT_PORT -RMI_PORT -JMS_PORT
Eg.
emca -config dbcontrol db -repos create -silent -PORT 1521 -SERVICE_NAME MESTEST -SYS_PWD SYS -SID MESTEST -DBSNMP_PWD dbsnmp -SYSMAN_PWD sysman -DBCONTROL_HTTP_PORT 1158 -AGENT_PORT 3938 -RMI_PORT 5521 -JMS_PORT 5541
Eg.
emca -config dbcontrol db -repos create -silent -PORT 1521 -SERVICE_NAME MESTEST -SYS_PWD SYS -SID MESTEST -DBSNMP_PWD dbsnmp -SYSMAN_PWD sysman -DBCONTROL_HTTP_PORT 1158 -AGENT_PORT 3938 -RMI_PORT 5521 -JMS_PORT 5541
Error accessing PRODUCT_USER_PROFILE
Error accessing PRODUCT_USER_PROFILE
Warning: Product user profile information not loaded!
You may need to run PUPBLD.SQL as SYSTEM
Solution: Run pupbld.sql at $ORACLE_HOME/sqlplus/admin
Warning: Product user profile information not loaded!
You may need to run PUPBLD.SQL as SYSTEM
Solution: Run pupbld.sql at $ORACLE_HOME/sqlplus/admin
Install Oracle 10R2 on SUN Solaris 10 X86-64
Download Oracle Database 10gR2 installer from http://www.oracle.com/technology/software/products/database/oracle10g/htdocs/10201solx8664soft.html
Checking the Hardware Requirements
1. Login as root.
2. To determine whether the system architecture can run the software,
# /bin/isainfo -kvThe result return should be "64-bit amd64 kernel modules"
3. Minimal 1024MB of physical RAM
# /usr/sbin/prtconf grep Memory
4. Minimal Swap
Between 512MB and 2048 MB 1.5 times the size of RAM
Between 2049 MB and 8192 MB Equal to the size of RAM
More than 8192 MB 0.75 times the size of RAM
# /usr/sbin/swap -s
5. To add additional swap, use mkfile to create a file suitable for a local swap area. For example, to create a 600MB swap file:
# /usr/sbin/mkfile 600m /swap
where /swap is the name of the file to be used as swap space. Units for the size can be kilobytes (k), blocks (b), or megabytes (m).
Tell the system to start using the file as swap
# /usr/sbin/swap -a /swap
Use swap -l to verify that the swap file has been activated.
6. Minimal 400MB of free space in /tmp and minimal 1.7GB of disk space for Oracle binaries
# df -k
Checking the Software Requirements
1. To check your solaris version,
# uname -a
2. To determine whether the required packages are installed
# pkginfo -i SUNWarc SUNWbtool SUNWhea SUNWlibm SUNWlibms \ SUNWsprot SUNWsprox SUNWtoo SUNWi1of SUNWi1cs SUNWi15cs SUNWxwfnt
3. If any of the package is not installed, install the package from Solaris CD. Eg.
# pkgadd -d /cdrom/sol_10_1008_x86/Solaris_10/Product SUNWi1cs
# pkgadd -d /cdrom/sol_10_1008_x86/Solaris_10/Product SUNWi15cs
(Pls note that pkgadd -d required a full path follow by a space and package name)
4. Create the Oracle Inventory and DBA group
# groupadd oinstall
# groupadd dba
5. Create the Oracle Software Owner user
# useradd -s /bin/ksh -d /export/home/oracle -m -g oinstall -G dba oracle
# passwd oracle
6. Set Oracle environment parameter by modify $HOME/.profile
export ORACLE_BASE=/opt/apps/oracle
export ORACLE_HOME=$ORACLE_BASE/product/10.2.0/db_1
export ORACLE_SID=MESTESTexport ORACLE_TERM=vt100
export TNS_ADMIN=$ORACLE_HOME/network/adminexport EDITOR=vi
export TERM=vt100
PATH=$PATH:/usr/sbin:$ORACLE_HOME/bin:$ORACLE_HOME/lib
7. Configuring Kernel ParametersIn Solaris 10, you are not required to make changes to the /etc/system file to implement the System V TPC. Solaris 10 uses the resource control facility for its implementation.
Note: Oracle Universal Installer(OUI) will give a warning on Kernel parameter because OUI is looking at /etc/system to check kernel parameter setting hence included below in /etc/system.
set shmsys:shminfo_shmmax=4294967295
set shmsys:shminfo_shmmni=128
set semsys:seminfo_semmni=128
set semsys:seminfo_semmsl=256
8. To modify the kernel parameters,
# projadd -U oracle -K "project.max-shm-memory=(priv,4096MB,deny)" user.oracle
# projmod -s -K "project.max-shm-ids=(priv,128,deny)" user.oracle
# projmod -s -K "project.max-sem-ids=(priv,128,deny)" user.oracle
# projmod -s -K "project.max-sem-nsems=(priv,256,deny)" user.oracle
Run Oracle Universal Installer
1. Login as oracle.
2. To view the values of kernel parameter,
$ prctl -i project user.oracle
3. To unzip Oracle Software,
$ unzip 10201_database_solx86_64.zip
4. Login as oracle in a xterm,
$ export DISPLAY=:0.0
$ cd /export/home/oracle/database
$ ./runInstaller
5. At the end of installation, run the scripts prompt as root
$ /opt/apps/oracle/oraInventory/orainstRoot.sh
$ /opt/apps/oracle/product/10.2.0/db_1/root.sh
Checking the Hardware Requirements
1. Login as root.
2. To determine whether the system architecture can run the software,
# /bin/isainfo -kvThe result return should be "64-bit amd64 kernel modules"
3. Minimal 1024MB of physical RAM
# /usr/sbin/prtconf grep Memory
4. Minimal Swap
Between 512MB and 2048 MB 1.5 times the size of RAM
Between 2049 MB and 8192 MB Equal to the size of RAM
More than 8192 MB 0.75 times the size of RAM
# /usr/sbin/swap -s
5. To add additional swap, use mkfile to create a file suitable for a local swap area. For example, to create a 600MB swap file:
# /usr/sbin/mkfile 600m /swap
where /swap is the name of the file to be used as swap space. Units for the size can be kilobytes (k), blocks (b), or megabytes (m).
Tell the system to start using the file as swap
# /usr/sbin/swap -a /swap
Use swap -l to verify that the swap file has been activated.
6. Minimal 400MB of free space in /tmp and minimal 1.7GB of disk space for Oracle binaries
# df -k
Checking the Software Requirements
1. To check your solaris version,
# uname -a
2. To determine whether the required packages are installed
# pkginfo -i SUNWarc SUNWbtool SUNWhea SUNWlibm SUNWlibms \ SUNWsprot SUNWsprox SUNWtoo SUNWi1of SUNWi1cs SUNWi15cs SUNWxwfnt
3. If any of the package is not installed, install the package from Solaris CD. Eg.
# pkgadd -d /cdrom/sol_10_1008_x86/Solaris_10/Product SUNWi1cs
# pkgadd -d /cdrom/sol_10_1008_x86/Solaris_10/Product SUNWi15cs
(Pls note that pkgadd -d required a full path follow by a space and package name)
4. Create the Oracle Inventory and DBA group
# groupadd oinstall
# groupadd dba
5. Create the Oracle Software Owner user
# useradd -s /bin/ksh -d /export/home/oracle -m -g oinstall -G dba oracle
# passwd oracle
6. Set Oracle environment parameter by modify $HOME/.profile
export ORACLE_BASE=/opt/apps/oracle
export ORACLE_HOME=$ORACLE_BASE/product/10.2.0/db_1
export ORACLE_SID=MESTESTexport ORACLE_TERM=vt100
export TNS_ADMIN=$ORACLE_HOME/network/adminexport EDITOR=vi
export TERM=vt100
PATH=$PATH:/usr/sbin:$ORACLE_HOME/bin:$ORACLE_HOME/lib
7. Configuring Kernel ParametersIn Solaris 10, you are not required to make changes to the /etc/system file to implement the System V TPC. Solaris 10 uses the resource control facility for its implementation.
Note: Oracle Universal Installer(OUI) will give a warning on Kernel parameter because OUI is looking at /etc/system to check kernel parameter setting hence included below in /etc/system.
set shmsys:shminfo_shmmax=4294967295
set shmsys:shminfo_shmmni=128
set semsys:seminfo_semmni=128
set semsys:seminfo_semmsl=256
8. To modify the kernel parameters,
# projadd -U oracle -K "project.max-shm-memory=(priv,4096MB,deny)" user.oracle
# projmod -s -K "project.max-shm-ids=(priv,128,deny)" user.oracle
# projmod -s -K "project.max-sem-ids=(priv,128,deny)" user.oracle
# projmod -s -K "project.max-sem-nsems=(priv,256,deny)" user.oracle
Run Oracle Universal Installer
1. Login as oracle.
2. To view the values of kernel parameter,
$ prctl -i project user.oracle
3. To unzip Oracle Software,
$ unzip 10201_database_solx86_64.zip
4. Login as oracle in a xterm,
$ export DISPLAY=
$ cd /export/home/oracle/database
$ ./runInstaller
5. At the end of installation, run the scripts prompt as root
$ /opt/apps/oracle/oraInventory/orainstRoot.sh
$ /opt/apps/oracle/product/10.2.0/db_1/root.sh
Download Oracle Opatch
To download OPatch, visit metalink and go to Patches & Updates and download patch 6880880.
Subscribe to:
Posts (Atom)