Posts

Oracle Exadata X8 Family overview

September 2019 Oracle announced Oracle Database Appliance X8-2 (Small, Medium and HA). ODA X8-2 comes with more computing resources compared with X7-2 Models. Let's take a quick look at few benefits of ODA followed by the technical specification on ODA X8-2 Small/Medium and HA. Oracle Database Appliance is an Engineered System. Software, server, storage, and networking, all co-engineered and optimized to run Oracle Database and applications. Benefits of Oracle Database Appliance (ODA): Software, server, storage, and networking engineered and optimized to run Oracle Database and applications. Supports Oracle Database Standard Edition, Standard Edition One, Standard Edition 2, and Enterprise Edition. Optimized for Cloud Capacity on Demand Licensing - Reduced Cost Ease of deployment, patching, management, and support Increased performance and reliability with NVMe flash storage Reliable hardware architecture with redundant power, cooling, networking, and storag...

About - Oracle Autonomous - Self Driving Database

What is Oracle Autonomous Database? Oracle Autonomous Database allows you rapidly & easily create mission critical databases, It protects data from both external and internal threats, automates all infrastructure & database maintenance, recovers from any failure without downtime and scales online for highest performance & lower cost. Components of Oracle Autonomous Database: An Oracle Autonomous database comprises of 3 components: Oracle Exadata Oracle database Automated Data Center Operations and Machine Learning   How Does Oracle Database Works: An Oracle Autonomous Database is self driving, self securing and self repairing. Self Driving:  It Automates all databases and infrastructure management, Patching, tune Queries and Monitoring Self Securing:  Protects database from both external and malicious internal users by automatically encrypting data both at rest and in transit Self Repairing:  Automatically recover from any failure. Protects fro...

Manual switchover of RAC database using Data Guard

The following post will provide the list of steps that needs to be performed while performing a manual switchover to DR database when Data guard is configured between these database. These commands are helpful if we are not using broker for switchover operations: Primary DB -  ERPDB Standby DB  DERPDB*   STEP1:(ERPDB) srvctl status database -d ERPDB srvctl stop instance  -d ERPDB  -i ERPDB2 -o immediate srvctl status database -d ERPDB STEP2: (DERPDB) srvctl status database -d DERPDB srvctl stop instance  -d DERPDB  -i DERPDB1 -o immediate srvctl status database -d DERPDB STEP3:(ERPDB) SELECT  NAME,DB_UNIQUE_NAME,DATABASE_ROLE,SWITCHOVER_STATUS FROM V$DATABASE; STEP4:(DERPDB) SELECT  NAME,DB_UNIQUE_NAME,DATABASE_ROLE,SWITCHOVER_STATUS FROM V$DATABASE; STEP5:(ERPDB) - Convert ERPDB to Physical standby database ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY WITH SESSION SHUTDOWN; SHUTDOWN IMMEDI...

Solaris 11.4 pkg publisher error - UnknownSysrepoConfiguration

Recently installation Solaris 11.4 operating environment where the repository was successfully confiured and installed started reporting the following errors when we were trying to install the new packages using the same repository. The following Error message is reported while we are trying to use the locally configured repository: root@ECMDB:~# pkg publisher Traceback (most recent call last):   File "/usr/bin/pkg", line 6702, in handle_errors     __ret = func(*args, **kwargs)   File "/usr/bin/pkg", line 6584, in main_func     api_inst = __api_alloc(mydir, provided_image_dir, pkg_image_used)   File "/usr/bin/pkg", line 1459, in __api_alloc     exact_match=exact_match)   File "/usr/lib/python2.7/vendor-packages/pkg/client/api.py", line 370, in __init__     cmdpath=self.cmdpath)   File "/usr/lib/python2.7/vendor-packages/pkg/client/image.py", line 236, in __init__     progtrack)   File "/usr/...

Oracle 12c Database installation Error on solaris sparc mini cluster

On solaris sparc mini cluster the database  home installation pre-eq checks were failing with following errors, though these errors are not reported during installer checks. A00100 OS Type              RECORD  SunOS SPARC 2.11 64-bit A00200 OS Certified?        PASSED  Certified A00210 Got Maint Updates?   FAILED  NoMaintUpd A01010 ApplTierDirectory    RECORD  /u01 A01020 A_T Valid?           PASSED  ATexists A01030 A_T Permissions OK?  PASSED  CorrectPerms A01040 A_T Disk Space       PASSED  Available A01400 Got Software Tools?  PASSED  tools_found A02020 ulimits OK?          FAILED  NoFilesTooSmall StackTooSmall A02210 Kernel Params OK?    PASSED  KernelOK A03010 Space in tmp         PASSED  Available A03510 IP ...

Database add node on EBS R12.2 fails RC-5004

Scaling of Database Instance for Oracle EBS R12.2 failing with the below listed Error: StackTrace: java.lang.NullPointerException         at oracle.apps.ad.context.CloneContext.preserveOldPortSettings(CloneContext.java:5527)         at oracle.apps.ad.context.CloneContext.promptForPortPool(CloneContext.java:5716)         at oracle.apps.ad.context.CloneContext.getInputDBRACInitial(CloneContext.java:3389)         at oracle.apps.ad.context.CloneContext.getInputFromUsers(CloneContext.java:2226)         at oracle.apps.ad.context.CloneContext.doClone(CloneContext.java:959)         at oracle.apps.ad.context.CloneContext.main(CloneContext.java:8059) RC-50208: Warning: Exception  in method preserveOldPortSettings Raised by oracle.apps.ad.context.CloneContext Started testing the availabilty of ports in port pool 6  Checking  Database Port on dc2prpn...

ORA-00304: requested INSTANCE_NUMBER is busy

While starting one of the cluster instance we encountered following error: SQL> startup nomount pfile='initPROD2.ora' ORA-32006: BACKGROUND_DUMP_DEST initialization parameter has been deprecated ORA-00304: requested INSTANCE_NUMBER is busy SQL> exit Disconnected Here we are trying to start instance on node2 and getting this error message, the error message is very clear that the instacne number which we are trying to mount is not available and is already mounted on other instance. SQL> set pages 300 lines 300 SQL> select inst_id, instance_number, instance_name, host_name, status from gv$instance;    INST_ID INSTANCE_NUMBER INSTANCE_NAME    HOST_NAME                                                        STATUS ---------- --------------- ---------------- -------------------------------------------------...