Created by: Ben Sunderland on 06-07-2012 02:57:32 AM 1. RDBMS node failed - am trying to get it to start with only 8 instead of 16GB - can this work ? 2. If I need to redeploy RBMS, do I still have to clean puppet master like with 2.5.2 - reason I ask is after it failed first time, I redployed without touching puppet , and the logs on director didn't update with the second deployment attempt. EDIT: Re 2) looks like cleaning puppet worked (or was co-incidence). Was able to redeploy (i.e. I got fresh logs for RDBM on director after sudo puppetca --clean <RDBMS_FQDN> Still, Re 1) the delpoyment failed with same erro as first time :
Jul 6 06:49:58 awq2rdb01 admin: SEVERE: Jul 6 06:49:58 awq2rdb01 admin: Database instance is unavailable. Fix the ORA error thrown and run EM Configuration Assistant again. Jul 6 06:49:58 awq2rdb01 admin: Jul 6 06:49:58 awq2rdb01 admin: Some of the possible reasons may be : Jul 6 06:49:58 awq2rdb01 admin: Jul 6 06:49:58 awq2rdb01 admin: 1) Database may not be up. Jul 6 06:49:58 awq2rdb01 admin: 2) Database is started setting environment variable ORACLE_HOME with trailing '/'. Reset ORACLE_HOME and bounce the database. Jul 6 06:49:58 awq2rdb01 admin: Jul 6 06:49:58 awq2rdb01 admin: For eg. Database is started setting environment variable ORACLE_HOME=/scratch/db/ . Reset ORACLE_HOME=/scratch/db and bounce the database. Jul 6 06:49:58 awq2rdb01 admin:
Subject: RE: installing RDBMS v3 questions.. Replied by: Ben Sunderland on 12-07-2012 11:06:14 PM Answers I figured out. 1. No, you must give it 16 GB. 2. If re-issuing puppet certs is necessary (and its unclear on these scenarios) just clean the cert cache using the admin gui of the node in question, then clean the cert on puppet master, then do a service puppet debug on the node, and it should resynch. 3 . Yes that is latest OVA.
Subject: RE: installing RDBMS v3 questions.. Replied by: Manuel Michel on 19-07-2012 10:41:35 AM To point 1. : This relays to the fact, that in the db requires already itself 8 GB shared memory:
mount -t tmpfs shmfs -o size=8g /dev/shm
you can also verify the /etc/fstab file to see what's in there. If you hack a little bit around it would probably work with 8 GB in complete - but I would not recommend that, especially in a productive deployment.
thx
commands to modify memory target.
alter system set memory_max_target=8G scope=spfile; alter system set memory_target=8G scope=spfile; alter system set processes=1000 scope=spfile; alter system set open_cursors=2000 scope=spfile; alter system set session_cached_cursors=500 scope=spfile; alter system set cursor_sharing='SIMILAR' scope=spfile; alter system set event='44951 TRACE NAME CONTEXT FOREVER, LEVEL 1024' scope=spfile;
Subject: RE: installing RDBMS v3 questions.. Replied by: Ben Sunderland on 22-07-2012 09:31:52 PM I just tried reducing the mem targets per above , and shared mem too. Then reduced memory of VM from 16 GB to 4 GB and at boot up it says "at least 16GB memory is required" and then halts.
Can this script be turned off as this is a DEV / TEST box.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
