Oracle - SQL - MySQL DBA - Life Long Learning Experience

Assumption: ASM is installed as grid owner Database is installed as oracle owner  ( RAC configured ) Password file , spfile are stored in ASM Key Steps are as follows : Setting up ODATEST RAC to RAC Data Guard Primary Environment Configuration Standby Environment Configuration RMAN Duplicate Clone Primary to Standby Database On the Primary Database Configure Data Guard Register Single Instance Standby DB with Clusterware Convert the standby database to Oracle RAC Reconfigure the RAC Database Services for Data Guard Configure Data Guard Broker Testing the Data Guard Switchover Using Broker. Primary Environment Configuration The first step is to create the Primary Database using the ODA Manager Web Console on the Node 0 of the cluster. Wait while the database creation job completes. This will take approx. 10-20 Mins. Add the new Oracle SID to /etc/oratab on both of the Primary ODA nodes and check the statuso ( customized script)  output to show when database is up and r

Standby database process status: You can run following query on standby database to see what MRP and RFS processes are doing, which block of which archivelog sequences are being shipped or being applied. SQL> select process, status, thread#, sequence#, block#, blocks from v$managed_standby ; PROCESS   STATUS          THREAD#  SEQUENCE#     BLOCK#     BLOCKS --------- ------------ ---------- ---------- ---------- ---------- ARCH      CLOSING               1      69479     932864        261 ARCH      CLOSING               1      69480     928768        670 ARCH      CLOSING               2      75336     933888        654 ARCH      CLOSING               2      78079     930816        842 ARCH      CLOSING               1      69475     943104         79 RFS       IDLE                  0          0          0          0 ... RFS       RECEIVING             1      69481     688130       1024 MRP0      WAIT_FOR_LOG          2      78080          0          0

SQL SERVER – Event ID 107- Report Server Windows Service cannot connect to the report server database. Error with Report Server One of my clients reported an error which is the subject of the blog. In the event viewer they were seeing below error:     Event Type: Error Event Source: Report Server Windows Service (MSSQLSERVER) Event Category: Management Event ID: 107 Computer: SQLSERVER Description: Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database The error is generic because it doesn’t tell the exact error which is causing a connectivity error. My immediate question was that, are there any more errors? So, I asked them to look at Reporting Service Log file. Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database. The application domain WindowsService_17 failed to initialize. Error: Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseUnavailableException: The report se