Good morning all, I hope anyone can help me with this. I am trying to upgrade an Oracle RAC of two nodes from version 12.2 to 19c. As part of the prerequirements, I have applied the patch 28553832 in both nodes. Opatch and Kfod show both the same patches applied to both nodes Node 1 $crsctl query crs activeversion -f Oracle Clusterware active version on the cluster is [12.2.0.1.0]. The cluster upgrade state is [NORMAL]. The cluster active patch level is . $crsctl query crs softwarepatch Oracle Clusterware patch level on node scglvdoraci0010 is . $crsctl query crs releasepatch Oracle Clusterware release patch level is and the complete list of patches [26839277 27105253 27128906 27144050 28553832 ] have been applied on the local node. $ kfod op=patches --------------- List of Patches =============== 26839277 27105253 27128906 27144050 28553832 $ kfod op=patchlvl ------------------- Current Patch level =================== 1205374555 Node 2 $crsctl query crs activeversion -f Oracle Clusterware active version on the cluster is [12.2.0.1.0]. The cluster upgrade state is [NORMAL]. The cluster active patch level is . $crsctl query crs softwarepatch Oracle Clusterware patch level on node scglvdoraci0010 is . $crsctl query crs releasepatch Oracle Clusterware release patch level is and the complete list of patches [26839277 27105253 27128906 27144050 28553832 ] have been applied on the local node. $ kfod op=patches --------------- List of Patches =============== 26839277 27105253 27128906 27144050 28553832 $ kfod op=patchlvl ------------------- Current Patch level =================== 1205374555 However, when I run the runcluvfy I got this error /grid122/app/19.3.0/grid/runcluvfy.sh stage -pre crsinst -upgrade -rolling -src_crshome /grid122/app/12.2.0/grid -dest_crshome /grid122/app/19.3.0/grid -dest_version 19.0.0.0.0 -fixup -verbose Verifying Oracle patch:28553832 ... Node Name Applied Required Comment ------------ ------------------------ ------------------------ ---------- scglvdoraci0009 missing 28553832 failed scglvdoraci0010 missing 28553832 failed Verifying Oracle patch:28553832 ...FAILED (PRVG-1260, PRVG-1261) My question is how cluvfy is checking which patches are applied and why it is getting this error , when kfod and lsinventory in opatch show both that the patch is applied in both nodes. Would anyone in this scenario try to upgrade when the requirements are not passed ? Thank you

working on an oracle 19c 2-node rac cluster. we were running awr reports when we noted in sys.dba_hist_snapshot that the cluster nodes were in different time zones. We have validated that our s_crsconfig files on each server both show America/Los_Angeles as the time zone. timedatectl also shows that the nodes are both in the same time zone (America/Los_Angeles / PST8PDT). (1) How can I tell which time zone each node thinks it is in? (2) How can I resolve this so that both nodes agree on the time zone? Thank you.

I have an Oracle 11g RAC installation which I want to "unconfigure". This is a cloned machine which has an Oracle 11g RAC installation. I want to "reset" it (drop databases, configuration etc and keep only the binaries) so that I can re-configure it according to my new requirements. Oracle provides instructions on how to Unconfigure Oracle Clusterware without removing binaries , which as far as I understand refers only to the CRS (and I am not sure it applies to 11g). However I want the same procedure for the database too. Is there anything similar? Regards

Some references say quorum disk and vote disk are the same, but "quorum disk" name was used in older versions. But Oracle 19c documentation still use both the names, so I think there is a difference. Also, when to use quorum failure group and what is it? documentation says: > A quorum failure group is a special type of failure group that does > not contain user data. Quorum failure groups are used for storing > Oracle ASM metadata. A quorum failure group may also contain voting > files if those files are stored in a disk group that contains a quorum > failure group. Additionally, Oracle ASM uses a quorum failure group to > help determine if the disk group can be mounted in the event of the > loss of one or more failure groups. Ok, but, for example, we have a Oracle Clusterware running and there is no quorum failure group configured, so it seems it can be used or not. When to use it?

In the Oracle 12c documentation it was not clear what is the difference between the *srvctl start* and *srvctl enable* commands for services associated with a database. In the view **dba_service** a database that has a service already started, has the column *ENABLED* with *NO*, what I noticed is that when a RAC service has already started and you try to enable it, it informs you that it is already enabled. srvctl enable service -d mydb -s myservice PRCC-1010: myservice was already enabled PRCR-1002: Resource ora.mydb.myservice.svc is already enabled

We are using 4 node Oracle 10GR2 RAC in Windows x64. 3 instances of our database crashed today and later started normally. I started them by connecting (Remote Desktop) to individual instances and executing startup command in sqlplus. I can connect to database using SYS account but when I try to connect using application user account, I get following error: > An error was encountered performing the requested operation: > > ORA-01033: ORACLE initialization or shutdown in progress > 01033. 00000 - "ORACLE initialization or shutdown in progress" > *Cause: An attempt was made to log on while Oracle is being started up > or shutdown. > *Action: Wait a few minutes. Then retry the operation. Vendor code 1033 Interesting thing is my instances started and database are open according to following queries. SELECT * FROM GV$INSTANCE; SELECT * FROM GV$DATABASE; I tried to use following command thinking that there is a mistake. SQL> alter database open; alter database open * ERROR at line 1: ORA-01531: a database already open by the instance I also tried to control RAC node statuses using following command. srvctl status database -d DBNAME database status command is following: Instance DBNAME1 is running on node NODE01 Instance DBNAME2 is running on node NODE02 Instance DBNAME3 is running on node NODE03 Instance DBNAME4 is running on node NODE04 So I can connect to database using SYS account, but WHY not application user account? Situation resolved itself in 15 minutes. I can connect to database now. But there is nothing in the alert logs about this situation. Should I check additional places to learn about real problem? Is there anything I can do in similar situation? After a while, I understood why this is happening! Oracle executes following command which we can see in alert logs. ALTER DATABASE OPEN Some time later , We can see following line in alert.log Completed ALTER DATABASE OPEN Only after this line, we can connecto to database. Interesting thing is in this 4 node RAC , we need to wait for this event in all instances before database start serving.

I have a customer that have a RAC environment (2 nodes, database version is 11gR2). Clusterware version: [grid@server2 ~]$ crsctl query crs releaseversion Oracle High Availability Services release version on the local node is [11.2.0.4.0] [grid@server2 ~]$ crsctl query crs activeversion Oracle Clusterware active version on the cluster is [11.2.0.4.0] Their aplication not use correctly the TAF (transparent application failover) After some research I've tested using swingbanch and I've found the same behavior in my LAB environment: INST_ID USERNAME SERVER SERVICE_NAME PROGRAM STATUS FAILOVER_TYPE FAILOVER_M FAI ---------- ---------- --------- -------------------- -------------------- -------- ------------- ---------- --- 1 SOE DEDICATED mootdb_prod JDBC Thin Client ACTIVE NONE NONE NO 1 SOE DEDICATED mootdb_prod sqlplus.exe INACTIVE SELECT BASIC NO 1 SOE DEDICATED mootdb_prod JDBC Thin Client ACTIVE NONE NONE NO 1 SOE DEDICATED mootdb_prod JDBC Thin Client ACTIVE NONE NONE NO 1 SOE DEDICATED mootdb_prod JDBC Thin Client ACTIVE NONE NONE NO 1 SOE DEDICATED mootdb_prod JDBC Thin Client ACTIVE NONE NONE NO 1 SOE DEDICATED mootdb_prod JDBC Thin Client ACTIVE NONE NONE NO 2 SOE DEDICATED mootdb_prod JDBC Thin Client ACTIVE NONE NONE NO 2 SOE DEDICATED mootdb_prod JDBC Thin Client ACTIVE NONE NONE NO 2 SOE DEDICATED mootdb_prod JDBC Thin Client ACTIVE NONE NONE NO 2 SOE DEDICATED mootdb_prod JDBC Thin Client ACTIVE NONE NONE NO 2 SOE DEDICATED mootdb_prod JDBC Thin Client ACTIVE NONE NONE NO 2 SOE DEDICATED mootdb_prod JDBC Thin Client ACTIVE NONE NONE NO 2 SOE DEDICATED mootdb_prod JDBC Thin Client ACTIVE NONE NONE NO 2 SOE DEDICATED mootdb_prod JDBC Thin Client ACTIVE NONE NONE NO 2 SOE DEDICATED mootdb_prod JDBC Thin Client ACTIVE NONE NONE NO The only session using the TAF above is a session created manually from sqlplus (failover_type column). I'm using the same tnsnames alias in all sessions. Why is this happening. Is there some requirement in the application side as well for it work correctly?

In my envoriment I am getting the following erro: ORA-15032: not all alterations performed ORA-15017: diskgroup "OCR" cannot be mounted ORA-15040: diskgroup is incomplete The problem is: I already has droped this diskgroup (I've changed the OCR diskgroup to another diskgroup OCR_NEW). I have two instances, in the first instance it's everything ok, but in the second instance I get this erro. Where can be the problem? I didn't find anything. I already tried to disable before to try remove in srvctl command, but not work as well. [oracle@server2 trace]$ srvctl disable diskgroup -diskgroup OCR PRCA-1000 : ASM Disk Group OCR does not exist PRCR-1001 : Resource ora.OCR.dg does not exist

what will happen, if we miss the '+' sign while adding datafile to ASM in oracle 11g database? Whether datafile added will be ASM based or Non-ASM based?

I am trying to install GI 19c on Oracle Linux 7 (required for 19c), and have used AsmLib to try to achieve device persistence (owner,group) for ASM devices/disks. Prior to that I used udev rules for the same and was able to achieve the same. Both times I get the same issue while doing ASM disk discovery as explained below. Problem is when I try to invoke the gridSetup.sh from node 1, all checks pass including node readiness, ssh equivalence, scan etc, but the installer fails(not able to find the disks) at discovering ASM disks which are already marked by oracleasm(AsmLib) as asm disks and are owned by grid:oinstall. The installer logs from oui show the below. WARNING: [May 29, 2019 12:32:14 PM] SRVCTL not found as there is no Grid Infrastructure home on the box. INFO: [May 29, 2019 12:32:14 PM] Executing [/u01/app/19.0.0/grid/bin/kfod.bin, nohdr=true, verbose=true, op=dfltdstr] INFO: [May 29, 2019 12:32:14 PM] Starting Output Reader Threads for process /u01/app/19.0.0/grid/bin/kfod.bin INFO: [May 29, 2019 12:32:14 PM] The process /u01/app/19.0.0/grid/bin/kfod.bin exited with code 1 INFO: [May 29, 2019 12:32:14 PM] Waiting for output processor threads to exit. INFO: [May 29, 2019 12:32:14 PM] Parsing Error 49802 initializing ADR INFO: [May 29, 2019 12:32:14 PM] Parsing ERROR!!! could not initialize the diag context Already tried setting ORACLE_BASE env variable and added to path, so adrci is executable. Also verified owner and permissions, (oracle:oinstall) Also checked on permissions for /u01/app/19.0.0/grid/bin/kfod.bin and they are executable by grid user.(grid:oinstall) Also tried various different asm diskstrings like ORCL:VOL*, ORCL*, VOL*, /dev/oracleasm/disks/* etc, but none of them worked. FYI: This is a fresh install of 19c GI onto a 2 node RAC cluster, (2 freshly created virtualbox machines with shared disks) with no prior GI or RDBMS installations on. Any help/assistance is greatly appreciated. Thanks

Where does SYSTIMESTAMP come from in multi-server Oracle RAC environment? I'm hoping that the SYSTIMESTAMP derives from a common location (master node?) as opposed to the server that is currently servicing the request. Additional Detail: -------------------- We are using a timestamp to ensure that entries in a log table are recorded sequentially. Say, for example, we have two nodes in our RAC and they are 1 second off. Our app server inserts two log entries within, say, 0.03 seconds of each other. The first insert is serviced by Node1 and the second by Node2. If there is one second difference between the two nodes, the timestamp could potentially show the log entries occurring in the wrong order! (I would just use a sequence, but our sequences are cached for performance reasons... )

please, can you clarify this? My configuration is RAC 12c on ASM on SLES 11 SP 4 on SystemZ. The nodes **rac11** and **rac12** are the server nodes of the primary database, named "primdb", uniq_name is "primdb". The instance names are **prim1** and **prim2** correspondingly. The nodes **rac21** and **rac22** are nodes of the standby database named "primdb", uniq name is "stdbydb". The instance names are **stdby1** and **stdby2** correspondingly. So, I'm trying to create physical standby using RMAN active duplication. After configuring such parameters as log_archive_dest, dump_dest, and so on I copied password file to the standby server and changed init-file. I added static entry to the listener on **rac21** (not SCAN-address) with service name of the **stdby1** instance and was able to connect to "nomount" database as SYS from any of my servers. $>su - oracle $> . oraenv ORACLE_SID = [oracle] ? stdby1 ORACLE_HOME = [/home/oracle] ? /u01/app/oracle_home The Oracle base has been set to /u01/app/oracle_base $>sqlplus / as sysdba SQL>startup nomount pfile='/tmp/initstdby1.ora' after that i perform the following: $> rman target sys/q1@primdb auxiliary sys/q1@stdby1 > connected to target database: PRIMDB (DBID=636407725) > connected to auxiliary database: PRIMDB (not mounted) $>duplicate target database for standby from active database nofilenamecheck; And on the step of executing memory script (sorry, i can't paste all RMAN output here) a wild error appears > RMAN-00571: > =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS > =============== RMAN-00571: =========================================================== RMAN-00554: initialization of internal recovery manager package failed > RMAN-04006: error from auxiliary database: ORA-00600: internal error > code, arguments: [kzsrsea_ext], [], [], [], [], [], [], [], [], [], > [], [] > -------------------------------------------> After that i'm not able to connect to this nomount database using sql*Net, the same error ORA-600 appears . The only way to connect to this database instance is to connect locally sqlplus / as sysdba And the interesting moment - if i copy the passwordfile again from the primary database to standby, i can connect to this standby database instance. So i think, that RMAN changes my passwordfile on the standby server. I searched for the same error on MOS (Doc ID:1136834.1 ), but they suggest to use backups as the workaround, which is not suitable for me. Any help would be much appreciated..

The application team claims there was a statement that took about 30s to execute at about a certain time. I tried to find out what queries had been executed in during this time with the following statement: select a.sql_id, sample_time from dba_hist_active_sess_history a, dba_hist_sqltext b where sample_time between to_date('20170330:13:15','yyyymmdd:hh24:mi') and to_date('20170330:13:25','yyyymmdd:hh24:mi') and b.sql_id=a.sql_id order by 2; However, only statements concerning rman, or the cloud control agent show up and no statement that seems to be from the application. Could it be that some queries executed do not show up in the dba_hist_active_sess_history table and where else could I look for it?

Is it possible to keep one node running in 2 node cluster while keeping one node down for Maintenance?.I want to do this as we are planning some hardware upgrades.

The Enterprise Manager jobs on our RAC system recently started intermittently failing initialization with the following error: > Error evaluating parameter sources/security checks/locks ORA-06508: > PL/SQL: could not find program unit being called We have tried bouncing DBConsole, re-submitting the job from the library and even recompiling the package being referenced. This is happening to multiple jobs with about one execution in every ten scheduled succeeding. Any ideas on what can be tried or checked? **Update:** I've opened a SR with Oracle.

I have a two node RAC database running in OEL 7 server. If there is a need to change the IP addresses of the already running server to a new one, will that hamper the functioning of the database? What changes on the database front would I need to incorporate to implement this? Is it even possible in the first place to run the database after changing the IPs?

Even though split brain scenario occurs in both Oracle RAC and Percona's XtraDB Cluster, a two node cluster is allowed and split brain scenario is resolved in RAC but a two node is not recommended in Percona Cluster ( 3 nodes is recommended ). Why is it like that? Doesn't Percona resolve split brain happening in two node cluster? I know I'm comparing two different technologies.. but still if anyone could clear this out. Thanks!

I did some Googling and couldn't find an answer to this question more recent than a few years ago, so I thought I'd ask. Oracle's RAC feature offers load-balancing for both read and write transactions, as well as scale-out and high-availability without downtime (at least, as I understand it - we're about to deploy our first databases that use RAC, so we'll see how it goes). Is there any SQL Server feature set (or third party component you could install on top) that delivers equivalent functionality? We've always used Windows clustering, where a failover event causes about 20-30 seconds of SQL downtime - always tolerable, but not ideal. Now, with AlwaysOn in SQL 2012, SQL Server shrinks that to about 15 seconds and adds the concept of read-only-secondary databases, but they still require that write transactions are choked through a single connection point (much improved, since many transactions are just read, but still not really load balancing), and in the case of a node failure or the need to patch, there's still downtime. I suppose it's just more curiosity - I feel like this is the only area that SQL Server falls behind Oracle (at least among the features I've personally seen used). I wanted to see if there are any options out there to close that gap and possibly improve our own SQL Server deployment while we wait for Microsoft's equivalent feature to be added - maybe in SQL 2014/2015?

A unit test requires a dbms_scheduler job to run on the same RAC node as the unit test is being run from. I know that with an Admin managed database this could be done by creating a service that limited the available instances and then using that service in a job class the job uses. My question is, how can this be done in 11.2 with policy management? Pools can be created that have only a single server in them and databases can be assigned to multiple pools, but as I understand it, a server can only be assigned to a single pool. Therefore, a service can't be created that uses a single server and still have other services that use a pool defined with multiple servers including that one. I also know that services can be created as either SINGLETON or UNIFORM, but since SIGNLETON doesn't provide for allowed servers or even preferred servers, I'm not sure how this would help. Surely I am missing something that makes this all possible.

Best practices for Oracle 11gR2 Data Guard implies that the primary and standby databases should have the same layout, eg. RAC to RAC. What special considerations would one need to take into account to replicate a RAC database to a single node physical standby? Any reason why this would be a very bad idea?