Could you actually let us know what exact command you used to shutdown the database. Also give us the full alert log content after you issued shutdown.
ORA-1013 would normally arise when you press Ctrl + C after issuing a command at sqlplus prompt..
I have seen dbca taking time when all options like JVM,XML , OLAP are chosen. By default all these are checked in and you have to uncheck them if you do not want it. Did you see the place where DBCA was taking more time? was it during data dictionary creation phase?
Just to add to Suarabh’s reply. You can audit select’s in database using schema level auditing. e.g audit select on employees will log selects on the employee table.
In case of FGA ,we can do fine grained auditing i.e we can define filters and also do auditing at column level.
1) Yes, you need to use only one ASM and CRS version.
2) Yes, in this case it will support 10.2 and 10.1 databases
3) Yes it can support. But again if there is any feature which is available in newer release , you will not be able to use it with lower release database. Starting from 11g, you have COMPATIBLE.ASM and COMPATIBLE.RDBMS disk group attributes which specify the compatibility settings for Oracle ASM and database instances. Check following for more detail
As we cannot run database with lower CRS/ASM version, so I would suggest that you upgrade the existing 10.2.0.2 CRS and ASM to 10.2.0.4 and then create new database in new DB home. So your configuration will look like
You can use the same Oracle home for creating database (use DBCA to create database). You do not require multiple homes for running multiple databases.
Even if you require two different Database Oracle homes, you can just install oracle database software in new home and use the same CRS for Clusterware.
Looking at description for error ORA-2970 we see following
<br />
oerr ora 29760<br />
29760, 00000, "instance_number parameter not specified"<br />
// *Cause: The init.ora file did not contain a value for the instance_number<br />
// which is required to identify this instance to other instances of<br />
// the database running on the same cluster<br />
// *Action: Assign a value to the instance_number parameter in the init.ora<br />
// parameter file<br />
So it looks like the instance_number parameter is not specified. Or it could be that instance is not able to access the correct spfile. Is your ASM spfile on OCFS? If yes, can you check if it can access it.
This blog reflect our own views and do not necessarily represent the views of our current or previous employers.
The contents of this blog are from our experience, you may use at your own risk, however you are strongly advised to cross reference with Product documentation and test before deploying to production environments.
Recent Comments