Database Technologies...!

DB - Oracle 11.2.0.3 OS - Windows server 2008 In the process of migrating a database from 10g to 11g on windows, it was required for us to create rman backup schedule  using DBMS_SCHEDULER. In 10g also, we were using DBMS_SCHEDULER so we were hoping to use same job definition in 11g, but with 11g there has been changes in the dbms_scheduler. In 10g we have used a .bat script which will run a rman script inside it to do a full backup of database. So in 10g job defined with job_type “EXCUTABLE” and job_action pointing to the .bat file did the trick. In 11g also we needed to do the same. But mainly two differences were there. 1 – We can not directly provide .bat file for the job_action. 2    If OracleJobScheduler<DBID>  windows service is not started, Then “Credentials” must be used So the solution was the below job definition with use of credentials and also using arguments for providing the location of bat file. begin dbms_scheduler.create_schedule( sched

DB - Oracle 9 OS - AIX Tools - Netbackup We have a 9i database which acts as a BCV and kept in read only mode. As per our client agreements we need to do restoration testing for each of the database in every 3 months time. Below is the process we used when restoring raw device based read only database (With Stand by Control file) using netbackup. Step 1- Restore oracle home to target database and do the needed changes in parameter file accordingly Restore the oracle home to target server (If you have same oracle_home as the source in target already this is not required). Then edit the parameter file accordingly. Follow ( http://dbtechno.blogspot.com/2012/11/restore-rman-full-backup-on-different.html - step3) Then mount the database. SQL>alter database mount standby database Standby since we are using a standby control file. Step 2 – Create required raw devices in target host Here you need to identify the required tablespaces/logs you are going to restore and the

DB2 v9.1 fixpsck 10 - Single Instance on AIX Issue - Can not connect to db2 database directly from server it self. (Remote connection were allowed) Error returned was as below. Any db2 command failes with same error. Since the remote connection are allowed, and only local connections were refused it was obvious that this was not caused by network error/port mismatch etc.. So we were checking for any server changes made and found that the OS admin has changed the "/etc/service" file in the process of SHC gap closing. Cause - While the SHC OS admin has removed the db2 FCM (Fast communications manager) related entries from /etc/services. Which was causing the error. What is FCM - FCM is the mechanism used by DB2 to communicate within database partitions in a DPF environment. Solution - Add the FCM port entries in  "/etc/service". This entries should have port range defined as in the below example. ( cat /etc/services | grep -i db2 ) The difference bet