Database Install/Upgrade/Opatch (MOSC)

MOSC Banner

Upgrade Issue, part 2 - component status

edited Jul 6, 2017 5:00AM in Database Install/Upgrade/Opatch (MOSC) 2 commentsAnswered

First trial of upgrade 'mydbdev' to 12.1.0.2.0 SE-Two and noticing change of some component status.

Starting position:

Oracle 11.2.0.4.0 SE-One 64-bit

Oracle GI 12.1.0.2.0- stand-alone ASM, no RAC no clustering of any kind

Oracle Linux 6

Two servers. 

'srvrprd' running 1 database, 'mydbprd'

'srvrtst' running 2 databases, 'mydbstg' and 'mydbdev'

On a weekly basis, mydbstg is recreated from mydbprd, using rman 'duplicate database'.

On demand, mydbdev is also recreated from mydbprd, using rman 'duplicate database'.

For first upgrade trial, did a fresh duplicate of mydwdev from mydwprd, so all internals are the same.  Upgrade itself had some issues (see one of my previous threads) but seemed to complete and db is operable.  But comparing status of components raised some questions:

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center