RAC DB creation Notes

Any body has notes to create RAC DB , version is 10g Cluster & storage is Varitas
I am used to create RAC DBs with dbca on oracle Clusterware and ASM...How this is different on Varitas cluster and storage?

On the linux and windows environments there is the OCFS, which will give you a Cluster File System, so at this point you'll have a file system. But protection relies on the kind of redundancy you have configured for your shared storage. On the ASM issue, this performs tasks such as mirroring and stripping for load balancing and fail over.
ASM is a volume manager for Oracle Datafiles Only, so the difference is that Oracle scope is only at the database storage level, meanwhile veritas is a complete file system.
~ Madrid

Similar Messages

Error while running adcfgclone on APPS tier (ERROR: context creation not completed successfully)

I am getting below error while running adcfgclone on APPS tier
ERROR : Unable to set CLASSPATH
/corp_ex1/DRPM/drpmcomn/clone/bin/../jlib/classes111.zip: is missing
First Creating a new context file for the cloned system.
The program is going to ask you for information about the new system:
ERROR: context creation not completed successfully.
Please check /tmp/adcfgclone_29475.err file for errors
i copied classes111.zip from IAS_HOME to COMMON_TOP . Now I am getting below error
First Creating a new context file for the cloned system.
The program is going to ask you for information about the new system:
ERROR: context creation not completed successfully.
Please check /tmp/adcfgclone_30763.err file for errors

Please post the details of the application release, database version and OS.
ERROR: context creation not completed successfully
This is a generic error, please check the log files for details about the error.
Thanks,
Hussein

Document is in transfer for PO, creation not possible

Hi
We are using SRM 4.0 EC scenario. Recently we have been facing the subjected error 'Document is in transfer for PO, creation not possible' while making the confirmation in SRM. It is observed that this is happening mostly in case once we make GR and cancel and repost. Thru some other thread posted in forum, came to know taht we need to delete the entries in table "BBP_DOCUMENT_TAB" via FM ''BBP_DELETE_FROM_DOCUMENT_TAB''. I ran thei FM but found NO poitive results. Hope somebody can help me out. This error became very common in our production system
Thanks
Kiran

Hi Kiran,
Please, use the report CLEAN_REQREQ_UP to clear the entry made for the GR in BBP_DOCUMENT_TAB. The problem comes because there is an entry for the GR in the table probably from the previous creation.
Regards
Saravanan.
Please award if useful

GR Error: Document is in transfer for PO, Creation not possible

Hi Experts,
While posting a GR for PO, following error is being encountered,
'Document is in transfer for PO, Creation not possible'.
I checked the PR - PO. There are multiple GRs for the PO and all earlier GRs are posted successfully.
For posting a new GR this error is coming.
Any pointers?
Thanks in advance.
-Dhananjay

Hi Kiran,
Please, use the report CLEAN_REQREQ_UP to clear the entry made for the GR in BBP_DOCUMENT_TAB. The problem comes because there is an entry for the GR in the table probably from the previous creation.
Regards
Saravanan.
Please award if useful

Document is in transfer for purchase order.Creation not possible

Dear All,
We did partial confirmation in EBP and later when trying to do confiramtion for the remaining quantiy getting the message"document is in transfer for purchase order.Creation not possible"
We are taking this problem in production as well as in quality systems also.
What are possible reason and how to solve it.
kindly share your views.
Thank you.

Hi yshu,
use tcode bd87 in SRM to check for failed confirmation IDOC (type MBGMCR).
The double click the status record to see the exact cause of the failure.
Rectify the error. Then try to execute the IDOC from BD87 tcode.
For a few errors you may not be able to execute the IDOC but to create a new confirmation in SRM. In such cases, follow the below procedure..
There should be an entry for the confirmation in the transfer table BBP_DOCUMENT_TAB in SRM. Display the details.
Then run FM "BBP_DELETE_FROM_DOCUMENT_TAB" to delete the entry from the doc tab table.
Then post a new confirmation in SRM.
There is also a FM in SRM using which you can change the status of thefailed IDOC from 51 to 68 or 31.
Rgds,
MJ

Document in transfer for purchase order - creation not possible

Hi Experts,
we get this error when we do confirmation"'document in transfer for purchase order - creation not possible'"
any inputs are appreciated
Rg
sam

Hi All,
We have resolved the above problem.
When user does confirmation ,if it sucessfully created then there will be no entry in BBP_Document_tab table.If it's in error in process and next time when user tries to do GR then he will encounter a pop up message "Document in transfer for PO, creation not possible".
So we need to delete the entries from table BBP_DOCUMENT_TAB using FM BBP_DELETE_FROM_DOCUMENT_TAB.
Then check again in BBP_DOCUMENT_TAB now there will be noentry there...so now user can do the confirmation from SRM,he will not encounter this error now.
Thanks to all the ppl who has replied
sameer

Standby database creation notes by metalink

Can any body send me good Standby database creation notes by metalink.

Are you wanting to see notes for physical or logical standby and what Database version and OS?
Use the knowledge browser in Metalink and click the database link in the Support Categories section on the left of the page and select Dataguard under the High Availability Section on the resulting page.

Mess SR 053 - Creation not possible (Mapping for product already exist..

There is an error ocurring when the CIF is executed, this message I can see in the transaction SMQ1, the error " SR 053 - Creation not possible (Mapping for <product> already exists <product> ", the product really exists in APO but I don't know why this error occur because in this case the material should be updated. Anyone know why this error occur ?? and how can I fix ??
When I try to execute only this material in CFM2 no errors occur.
Regards,
Edson Suzuki

We did faced a similar problem. The reason was the external material number was different in both cases.
ie the already existing record has the external material number padded with '0000' and the one coming doesn't have leading '0000'
If this suggestion helps you, please reward by points..
Shibu

Is my db running in RAC mode or not?

Friends,
db: 10gR2 and 11gR2
In 10gR2 i dont have RAC. its a single instance db.
11gR2 i have 2 RAC Node.
i know the below command will show the difference.
select instance_number,instance_name,host_name from v$instance;
but i want to know whether there is any other way to find out whether my 10gR2 is in RAC mode or not?
thanks

906621 wrote:
Friends,
db: 10gR2 and 11gR2
In 10gR2 i dont have RAC. its a single instance db.
11gR2 i have 2 RAC Node.
i know the below command will show the difference.
select instance_number,instance_name,host_name from v$instance;
but i want to know whether there is any other way to find out whether my 10gR2 is in RAC mode or not?
thanksYou have to use gv$ views to get that information
sys@ORCL> select instance_name from gv$instance;
INSTANCE_NAME
orcl
sys@ORCL> show parameter cluster_database
NAME                                 TYPE        VALUE
cluster_database                     boolean     FALSE
cluster_database_instances           integer     1
sys@ORCL>also by using srvctl
$srvctl status database -d <db_unique_name>

In-place upgrade of Enterprise Manager for RAC databases is not supported

upgrading 2 node RAC from 10.2.0.1 to 10.2.0.3 on Windows 2003 64 bit. I got the following:
In-place upgrade of Enterprise Manager for RAC databases is not supported in this release
Now I cannot log in to the database control as sys with sysdba role . I get "invalid username/password" error
I can login as a dba user
I also get a java error after I log in, some thing about class not found, but then I'm in and I can do everything that I try, although I haven't tried scheduling a backup yet
Can I upgrade EM to 10.2.0.3?
If so, how?

On the patchset readme...
11.3 Upgrade of Oracle Enterprise Manager Not Supported
When you start Oracle Database Upgrade Assistant to upgrade 10.2.0.1 database to 10.2.0.3 patch set, the following error occurs:
Inplace upgrade of Enterprise Manager is not supported for RAC databases is not supported in this release
Workaround:
Ignore warning.
If you drop and recreate the EM repository?
1). emca -deconfig dbcontrol db repos drop
2). emca -config dbcontrol db -repos create
Be careful, doing this put the database on QUIESCE mode.
Regards,
Rodrigo Mufalani

Context creation not completed successfully. Please check /tmp/adcfg

I am running perl adcfgclone at the databaseTier of R12.0.4 and am getting below error please reply
PROMPT :
Target hostname (virtual or normal) [zishan]
ANSWER :
zishan
PROMPT :
Target system domain name
ANSWER :
TEST1
StackTrace:
java.lang.NullPointerException
at java.util.Hashtable.put(Unknown Source)
at oracle.apps.ad.context.CloneContext.getInputFromUsers(CloneContext.java:888)
at oracle.apps.ad.context.CloneContext.doClone(CloneContext.java:575)
at oracle.apps.ad.context.CloneContext.main(CloneContext.java:4647)
RC-50004: Error occurred in CloneContext:
null
Context file creation not succesful

Hi,
PROMPT :
Target system domain name
ANSWER :
TEST1Is TEST1 the correct domain name?
StackTrace:
java.lang.NullPointerException
at java.util.Hashtable.put(Unknown Source)
at oracle.apps.ad.context.CloneContext.getInputFromUsers(CloneContext.java:888)
at oracle.apps.ad.context.CloneContext.doClone(CloneContext.java:575)
at oracle.apps.ad.context.CloneContext.main(CloneContext.java:4647)
RC-50004: Error occurred in CloneContext:
null
Context file creation not succesfulPlease verify you have proper entry in the hosts file, and entry the correct domain name as the one you have in the hosts file.
RC-50004: Error Occurred In Clonecontext : At Java.util.Hashtable.put(Unknown Source) [ID 763587.1]
perl adcfgclone.pl dbTechStack fails with error RC-50004: Error occurred in CloneContext [ID 467659.1]
Clone Procedure For "Perl Adcfgclone.Pl Dbtechstack " Returns Error [ID 457814.1]
Thanks,
Hussein

Immediate Transfer Order Creation not occuring for Sales Document Type

Hello gurus,
I have a situation where a transfer order is not being created immediately for a specific sales document type.
Here is an example document flow of a desired scenario where the system is working:
Sales document type: ZOR
> Delivery type: LF
> WMS transfer order
The Item Category in this scenario is TAN.
Here is an example of the document flow in the current scenario where the system is not working:
Sales document type: ZPRD
> Delivery type: LF
The Item Category is also TAN in this scenario. The only identifiable difference in these scenarios is the sales document type. For the ZOR SaTY, a Transfer Order prints immediately once the delivery is created. For the ZPRD SaTY, a Transfer Order needs to be manually created after delivery creation.
Is there a configuration setting that is controlling this? Any help would be greatly appreciated.

Thank you very much for the link. When I insert the WMTA output type in the delivery output header, the Transfer Order is automatically created.
The problem I'm running into now is the configuration setting that controls this. I thought I figured it out when going to this IMG path:
SAP Customizing Implementation Guide --> Logistics Execution --> Shipping --> Basic Shipping Functions --> Output Control --> Define Print Parameters Shipping
When selecting the Delivery Note, the shipping point I was using was not configured in this location. I added the shipping point into this transaction, saved, and created a new order & delivery. However, the WMTA output type still was not automatically inserted into the delivery when saving. Is there another location I should be looking to fix this so that when I enter an order with a particular Shipping Point, the WMTA output type automatically appears in the delivery?

RAC: Service started not in the right instance

Hello,
I added today two instances (ACCMEAS3, ACCMEAS4) to a RAC databases (10gR2). The system has now 4 nodes. The new configuration of my service is:
$>-RAC>-ACCMEAS3:$ srvctl config service -d ACCMEAS
ACCMEAS_S PREF: ACCMEAS3 AVAIL: ACCMEAS4
$>-RAC>-ACCMEAS3:$srvctl status service -d ACCMEAS
Service ACCMEAS_S is running on instance(s) ACCMEAS3
This is the actual configuration in the CRS.
Nevertheless the ACCMEAS2 still has the service, despite I have bounced the instance:
(info from a listener):
Service "ACCMEAS_S" has 2 instance(s).
Instance "ACCMEAS2", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0 state:ready
REMOTE SERVER
(ADDRESS=(PROTOCOL=TCP)(HOST=nodea)(PORT=1574))
Instance "ACCMEAS3", status READY, has 2 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0 state:ready
REMOTE SERVER
(ADDRESS=(PROTOCOL=TCP)(HOST=nodeb)(PORT=1574))
"DEDICATED" established:1639 refused:0 state:ready
LOCAL SERVER
The only way to avoid this is to put ACCMEAS2 down.
The service is configured TAF: Basic-Select, CLB_GOAL: LONG,GOAL:NONE
The connection string for info purpose:
datab=(
     DESCRIPTION=
     (ADDRESS= (PROTOCOL=TCP) (HOST=nodea-v) (PORT=1574) )
     (ADDRESS= (PROTOCOL=TCP) (HOST=nodeb-v) (PORT=1574) )
     (ADDRESS= (PROTOCOL=TCP) (HOST=nodec-v) (PORT=1574) )
     (ADDRESS= (PROTOCOL=TCP) (HOST=noded-v) (PORT=1574) )
     (LOAD_BALANCE=off)
     (ENABLE=BROKEN)
     (CONNECT_DATA=
          (SERVER=DEDICATED)
          (SERVICE_NAME=accmeas_s)
          (FAILOVER_MODE=
               (TYPE=SELECT)
               (METHOD=BASIC)
In the future we would like to have all instances as possible spares, that's why this definition in the tnsnames.ora.
What makes the service to get started on a instance not defined for?
Thanks for your help!

The workaround I have found is to use dbms_service.stop_service. This stops the service on the instance 2 and makes everything coherent with the CRS.
Ruben

PO Creation not to be allowed in future date

Hi
Our Requirement is Po Creation in future date should not be allowed
Please suggest how it can be achieved
Regards
Sameer

Hi Sameer,
You need to set the message as error. for this you need to change the meaage attribute from warning to error
go To Materials Management>Purchasing>Environment Data>Define Attributes of System Messages
Regards,
Tushar Patankar

PI 7.4 java stack only, Acknowledgement creation not triggered

Hello everyone
I have one IDoc-To-File scenario working fine, including acknowledgements (ALEAUD) being sent back to the sending system. The message log in such cases looks like this:
But I have another IDoc-To-HTTP scenario for which the acknowledgement (ALEAUD) creation is not being triggered, thus the system that originally sends IDocs doesn't get back any acknowledgements. In the message details I can see this:
I believe that it is because of QOS = EO (async) and the http adapter continues (and fails) without waiting for a http status code coming back from the receiver.
Just to try it out I would like to set QOS to BE (best effort). How and where to achieve this?
Thanks anyone for some help!
Kind regards
Renaud

ok, in the message log I found this:
So this is clearly an error coming back from receiver system... sorry, didn't realize it somehow.
But still... why is no acknowledgement (ALEAUD) being triggered?
This is how I configured it in the Integration Builder and NWA:
Business System A with a sender communication channel B of adapter type IDoc_AAE
RFC Parameters = From NWA
Resource Adapter Name = A_RA
Ack Connection Factory Name (reuse NWA configuration) = A_CF
On the Ack Settings Tab I checked "System Ack Ok Requested" and "System Ack Error Requested" and "ALEAUD Special Handling Needed"
Connection from PI -> SAP ERP System A
In NWA I created a new Destination of type RFC called ACLNT<CLIENT> pointing to sender ERP system (A)
Connection Test (ping) is successful
Connection from SAP ERP System A to PI
In NWA I created a new Resource Adapter called A_RA and configured its properties like this:
Binding Key = PI_AAE_IDOC
destinationName = ACLNT<CLIENT>
gatewayServer = <IP of ERP system>
gatewayService = sapgw<instance n° of ERP system>
local = false
MaxReaderThreadCount = 5
multiRepository =
ProgramID = PI_4_A<CLIENT>
In SAP ERP system in SM59 I created a new RFC destination, type = T, as registered server program with same ProgramID (PI_4_A<CLIENT>)
Connection test (in SM59) is successful
To enable / allow acknowledgements...
I set the persistance parameter to true in the JavaIdocAdapter
I created a JCA Connection Factory on the outboundRA Resource Adapter. Within this JCA Connection Factory I put in Configuration Properties the destinationName = ACLNT<CLIENT> (the RFC Destination Name created earlier and pointing to the sending SAP ERP System A which should receive acknowledgement ALEAUD Idocs).
I did the same for the IDoc-2-File scenario mentionend in my 1st post... there acknowledgment messages are working fine.
Best regards
Renaud

RAC DB creation Notes

Similar Messages

Maybe you are looking for