Recently an interesting issue reported to me.
There was a case, where ORA-00955 was encountered while creating a custom MV on a EBS 12.2 environment.
The issue was reported through my forum: (Here is the link of the issue : http://erman-arslan-s-oracle-forum.2340467.n4.nabble.com/Another-interesting-issue-td1918.html)
I guess the environment in question was managed by following the new deployment standards of EBS 12.2. I mean the EBR and online patching related rules of the EBS 12.2 deployment processes were taking into account while deploying the customization and after an online patching session, it seems they started to get ORA-00955 while trying to create a custom MV.
The object in question was not in dba_object, but it was there sys._CURRENT_EDITION_OBJ with type# 10.
I wanted to be sure about the existence of the object and directly recommended to enable trace for it.
alter session set events '955 trace name errorstack level 10';
alter session set events '10046 trace name context forever, level 12';
The problem interestingly solved after running a full cleanup (adop phase=cleanup cleanup_mode=full), which taught us the following;
"adop full cleanup does all the cleanup tasks for objects and it is not only required after aborting an online patching cycle, but also in some other situations like the one described in this blog post"
There was a case, where ORA-00955 was encountered while creating a custom MV on a EBS 12.2 environment.
The issue was reported through my forum: (Here is the link of the issue : http://erman-arslan-s-oracle-forum.2340467.n4.nabble.com/Another-interesting-issue-td1918.html)
I guess the environment in question was managed by following the new deployment standards of EBS 12.2. I mean the EBR and online patching related rules of the EBS 12.2 deployment processes were taking into account while deploying the customization and after an online patching session, it seems they started to get ORA-00955 while trying to create a custom MV.
The object in question was not in dba_object, but it was there sys._CURRENT_EDITION_OBJ with type# 10.
I wanted to be sure about the existence of the object and directly recommended to enable trace for it.
alter session set events '955 trace name errorstack level 10';
alter session set events '10046 trace name context forever, level 12';
The problem interestingly solved after running a full cleanup (adop phase=cleanup cleanup_mode=full), which taught us the following;
"adop full cleanup does all the cleanup tasks for objects and it is not only required after aborting an online patching cycle, but also in some other situations like the one described in this blog post"
It is better to keep this in mind...
No comments :
Post a Comment
If you will ask a question, please don't comment here..
For your questions, please create an issue into my forum.
Forum Link: http://ermanarslan.blogspot.com.tr/p/forum.html
Register and create an issue in the related category.
I will support you from there.