09-06-2007
How to diagnosis the problem on Solaris 10 for DB startup
I run Oracle 10g on Solaris 10 Sparc machine. I created a dbora file to automatically start Oracle database when UNIX system reboot. I created this dbora file under /etc/init.d, Then link it to /etc/rc0.d/K10dbora and /etc/rc2.d/S99dbora. When I reboot solaris 10 system to test this script. It seems not working.
Then I used 'svcs -a' and see S99dbora legacy service did run at /etc/rc2_d. However, the database was not started up. I have checked scripts carefully. It was coding correctly. The same scripts and the same procedures have been implemented on other UNIX servers with oracle 10g DB. They are all working fine. Question is: how can I diagnosis where the problem is? How to find why the script was running and DB was not started up.Please advise me your thoughts and methods. Thanks a lot.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have installed free bsd, and it won't reboot on it.
I got win on disk 1 and on disk 2 is free bsd.
Is there an optoin tha do so u could choose betwen win or free bsd?
Is there an option in the installation that maybe I have missed? (4 Replies)
Discussion started by: Mr.Rudiment
4 Replies
2. UNIX for Dummies Questions & Answers
i have oracle database startup problem.
i have installed oracle8i(8.1.7) on windowsXP i have configured everything properly but i m unable to start database automatically and for this when i checked services of database it shows starting not started so i have to start it manually.Can u plz tell... (3 Replies)
Discussion started by: vandana
3 Replies
3. Shell Programming and Scripting
hi experts,
i have some problem with my solaris 8 v890 server, is :
the server running process called SS7 below is example process :
PID STAT MODE HOST MUX OBJECT
384 ok LX|A USSDGmdn-1a spm/0 daemon
385 ok LX|A USSDGmdn-1a spm/2 ... (0 Replies)
Discussion started by: bucci
0 Replies
4. Solaris
Hi,
I have Solaris 9 installed on a SunFire V880. When the machine boots up, I get a message, "the X-server cannot be started on display:0".
I searched the forum for possible solution, however, they are not applicable to my problem for two reasons: either the platform is different or the... (6 Replies)
Discussion started by: purveshkhatri
6 Replies
5. Linux
Hello:
I have a little problem, I have Windows Xp in my desktop, yesterday I installed centos 5. Now when the Pc starts it goes directly to windows and I do not have the option to start centos.
Xp and centos are in the same disk. (4 Replies)
Discussion started by: jcpetela
4 Replies
6. Solaris
Hello
How can I check to see when nis server is starting? I look at /etc/rc2.d/ but I don't see it in there.
Every time we have power outage problem. I have to start autof service manual. So I think it might have to do with nis server services. (1 Reply)
Discussion started by: congngo
1 Replies
7. UNIX for Advanced & Expert Users
Hi,
I am facing a strange issue. Application is deployed in a cluster with 2 Unix nodes (with same configuration). On one node the application is working fine but on another node we see this behavior I found using vmstat- when the server is not yet started everything is OK; when you start the... (3 Replies)
Discussion started by: ash.abrol
3 Replies
8. Solaris
Is there a way to debug the startup on a VT100 running Solaris 5? I have a problem related to file attributes that are resetting to there prior settings when the machine reboots. (3 Replies)
Discussion started by: jimcz2it
3 Replies
9. Solaris
Hi all,
I have a server in maintenance mode and need to boot it up. Its due to a broken service "RepX".
I need to stop the service from trying to start at boot up but i can't find where it is booting up from... it is not in any of the rcX.d directories and the two locations i have found it... (6 Replies)
Discussion started by: Tommyk
6 Replies
10. Hardware
Hello everyone,
I'm having an odd problem I've never encountered before and I'm at the point where the only things I have not replaced are the CPUs, Motherboard and Power Supply.
The errors:
: CPU:0 MC4_STATUS: 0xdc2b400013080a13
: MC4_ADDR: 0x0000000001017d80
: Northbridge Error (node... (5 Replies)
Discussion started by: WrinkledCheese
5 Replies
LEARN ABOUT DEBIAN
init.d
init.d(4) init.d(4)
NAME
init.d - initialization and termination scripts for changing init states
SYNOPSIS
/etc/init.d
/etc/init.d is a directory containing initialization and termination scripts for changing init states. These scripts are linked when appro-
priate to files in the rc?.d directories, where `?' is a single character corresponding to the init state. See init(1M) for definitions of
the states.
The service management facility (see smf(5)) is the preferred mechanism for service initiation and termination. The init.d and rc?.d direc-
tories are obsolete, and are provided for compatibility purposes only. Applications launched from these directories by svc.startd(1M) are
incomplete services, and will not be restarted on failure.
File names in rc?.d directories are of the form [SK]nn<init.d filename>, where S means start this job, K means kill this job, and nn is the
relative sequence number for killing or starting the job.
When entering a state (init S,0,2,3,etc.) the rc[S0-6] script executes those scripts in /etc/rc[S0-6].d that are prefixed with K followed
by those scripts prefixed with S. When executing each script in one of the /etc/rc[S0-6] directories, the /sbin/rc[S0-6] script passes a
single argument. It passes the argument 'stop' for scripts prefixed with K and the argument 'start' for scripts prefixed with S. There is
no harm in applying the same sequence number to multiple scripts. In this case the order of execution is deterministic but unspecified.
Guidelines for selecting sequence numbers are provided in README files located in the directory associated with that target state. For
example, /etc/rc[S0-6].d/README. Absence of a README file indicates that there are currently no established guidelines.
Do not put /etc/init.d in your $PATH. Having this directory in your $PATH can cause unexpected behavior. The programs in /etc/init.d are
associated with init state changes and, under normal circumstances, are not intended to be invoked from a command line.
Example 1: Example of /sbin/rc2.
When changing to init state 2 (multi-user mode, network resources not exported), /sbin/rc2 is initiated by the svc.startd(1M) process. The
following steps are performed by /sbin/rc2.
1. In the directory /etc/rc2.d are files used to stop processes that should not be running in state 2. The filenames are prefixed with K.
Each K file in the directory is executed (by /sbin/rc2) in alphanumeric order when the system enters init state 2. See example below.
2. Also in the rc2.d directory are files used to start processes that should be running in state 2. As in Step 1, each S file is executed.
Assume the file /etc/init.d/netdaemon is a script that will initiate networking daemons when given the argument 'start', and will terminate
the daemons if given the argument 'stop'. It is linked to /etc/rc2.d/S68netdaemon, and to /etc/rc0.d/K67netdaemon. The file is executed by
/etc/rc2.d/S68netdaemon start when init state 2 is entered and by /etc/rc0.d/K67netdaemon stop when shutting the system down.
svcs(1), init(1M), svc.startd(1M), svccfg(1M), smf(5)
Solaris now provides an expanded mechanism, which includes automated restart, for applications historically started via the init script
mechanism. The Service Management Facility (introduced in smf(5)) is the preferred delivery mechanism for persistently running applica-
tions. Existing init.d scripts will, however, continue to be executed according to the rules in this manual page. The details of execution
in relation to managed services are available in svc.startd(1M).
On earlier Solaris releases, a script named with a suffix of '.sh' would be sourced, allowing scripts to modify the environment of other
scripts executed later. This behavior is no longer supported; for altering the environment in which services are run, see the setenv sub-
command in svccfg(1M).
/sbin/rc2 has references to the obsolescent rc.d directory. These references are for compatibility with old INSTALL scripts. New INSTALL
scripts should use the init.d directory for related executables. The same is true for the shutdown.d directory.
17 Aug 2005 init.d(4)