RecoveryAreaDestination=/oradata/recovery Note that we used the general purpose template, then changed the settings to meet the requirements for OEM: gdbName=emrep The non-default settings for the DBCA response file are below. runInstaller -silent -responsefile /u01/software/database/response/install.rsp –ignoreSysPrereqs The command used to install the database software was. The non-default options we used for the database silent install were: =INSTALL_DB_SWONLY We are covering the steps for the silent installation and database creation quickly, in order to cover the OEM software installation in detail. Since we had the same issue with all of the Oracle installers, we had to use the silent install method for both the database software install and database creation. Regardless, I did not have time to track the problem down in deep detail, so a silent install became my only option.įortunately, the basic instructions that Oracle provides for an OEM silent install are fairly decent, though as is typical with Oracle, they leave out a certain amount that you need to figure out for yourself. Both the database software and the OMS software came up in a character set (shown in the figure above), so I expect it was a problem with the server setting. I didn’t get the chance to really track the source of the original problem, which was that the Oracle GUI installer was running in some unknown character set.īecause of this, it became necessary to complete the installation using a silent install. I ran into an interesting problem at one of our customer sites the other day.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |