RunOneWorld.sh

mcb

Active Member
Hi!!,

I can't start the OneWorld services, I have a conflict with IPC and Ihave changed twice the value in JDE.INI on the Solaris Server.
Please, Anybody know my problem?.
Thanks in advance.
 
mcb,

Questions / things for you to check:

0. What OneWorld version(s) are you running?

1. Are you in production or just starting your implementation?

2. Do you have more than 1 version of OneWorld on your Enterprise Server? e.g are you in the midst of installing XE while still running an older version?

3. Are you logged in with the proper unix JDE account (the one that should set all environment variables properly)?

4. Did you run EndOneWorld.sh first, even though you didn't think OneWorld was running?

5. Does your EndOneWorld.sh include running rmics.sh? If not try running it once or twice.

6. Have you rebooted the Sun box (sometimes is neccessary once things get really bollixed up)?

7. Have you looked at the log files on the server to see what errors are being reported. What errors are those?

8. What/where is the IPC conflict?

9. What else has changed recently besides the starting IPC key value?

10. Is Oracle running?

Cheer up! We'll get the beast running (assuming it used to run).

Larry Jones
[email protected]
OneWorld B733.1, SP 11.3
HPUX 11, Oracle SE 8.1.6
SandBox: OneWorld XE SP15
 
Hi!!,
1. Version B7332 SP11.3
2.Just implemantation
3.I have just only one version on my server.
3. I'm logging with jdeb7332.
4. Yes I did.
5. No I run first EndOneWorld and after rmics.sh.
6. No I haven't
7. The errors refers to IPC and Scheduler doesn't run.
8. When I execute the RunOneWorld, appears a message that say "there is IPC conflict, you may need to change the value of StartIpcKeyValue in JDE.INI, or your variable JDE_BASE may be set incorrectly".
9. In DE10, I have change the numberOfAutoStartProcesses from 0 to 1, in JDE.INI file.
10. Yes of course.
Thank you very very much!!,
I hope it runs!!!
6.
 
Can you post the contents of the Sun box's JDE.INI file please.

Also please verify that all processes owned by jdeb7332 are down (ps -fu jdeb7332) after running EndOneWorld.sh


Larry Jones
[email protected]
OneWorld B733.1, SP 11.3
HPUX 11, Oracle SE 8.1.6
SandBox: OneWorld XE SP15
 
Try this in your jde.ini on the Enterprise server:

[JDEIPC]
ipcTrace=0
;CLSID=
;startIPCKeyValue=IIIII
startIPCKeyValue=7001

This is from an NT Enterprise server where you don't actually have to set
the IPC start value. However, setting it seems to clear a few of the jde
logs.

Colin





Colin Dawes, MSc
City of Guelph
B7332 SP13.1, Oracle 8.1.6, NT 4.0, Fat & WTS
 
Maite,

I received your email of the .ini file and your logs. The jdedebug log seemed fine - no specific IPC errors. The jde log showing the scheduler not starting is something to be adressed but not critical to OneWorld running.

More Questions:
1. after running RunOneWorld.sh are any jdeb7332 processes running? Which ones? are any UBE processes running?

2. Have you tried running PortTest?

3. What is the value of the JDE_BASE environment variable? (type env at the UNIX shell prompt)

4. Have you rebooted yet?

Some things jumped out at me in your JDE.INI file (attached for others on the forum to view). I list correct settings to things I saw below:

[SVR]
EnvironmentName=CRP733 [not CRPB733]

[Lock Manager]
Server=CPDESA
AvailableService=TS

[Security]
DefaultEnvironment=CRP733 [should match other settings in this file]
SecurityServer=CPDESA

Try these and see what happens (and don't forget to boot!).


Larry Jones
[email protected]
OneWorld B733.1, SP 11.3
HPUX 11, Oracle SE 8.1.6
SandBox: OneWorld XE SP15
 
When you run EndOneWorld you get IPC conflicts?

You must get return values when you run rmics.sh is that correct?

Probably a list of process id's and their owners?

If so, these are your conflicts and you will need to kill these processes
before you can restart services cleanly....

Good luck
 
Try changing the start value to a high value like '20001' and check


----Original Message Follows----
From: mcb <[email protected]>
Reply-To: [email protected]
To: [email protected]
Subject: RunOneWorld.sh
Date: Thu, 10 May 2001 07:57:15 -0700 (PDT)

Hi!!,

I can't start the OneWorld services, I have a conflict with IPC and Ihave
changed twice the value in JDE.INI on the Solaris Server.
Please, Anybody know my problem?.
Thanks in advance.


--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=OW&Number=10540
 
mcb,
You must be the jdeb7xxx user (where x relates to your specific
release of OneWorld) in order to stop and/or start OneWorld services.
It's best to log in as root and 'su' to the jdeb7xxx user, then go to
/oneworld/b7332/system/bin32 directory. From here you will type
'RunOneWorld.sh or EndOneWorld.sh' (or you can use the
./EndOneWorld.sh). Be sure that your database is up and running and
that the listener is up and running. (Older versions of OneWorld i.e.
B732.2 had listener problems quite often). If the database and listener
are not up you probably won't be able to start services.
This information is geared towards HPUX platform but should be very
similar for the Solaris platform.
Hope this helps.

Lisa G. Stinebuck
Senior Service Delivery Technician
Logical EBOC Cincinnati
513-412-7950 x1021
[email protected]
 
Re: RE: RunOneWorld.sh

I have to correct your post on this Lisa.
Logging in as root and then 'su' to the jdeb7xxx user typically will not execute login scripts (such as .profile). As a result environment variables such as JDE_BASE will not get set.

regards,



Larry Jones
[email protected]
OneWorld B733.1, SP 11.3
HPUX 11, Oracle SE 8.1.6
SandBox: OneWorld XE SP15
 
RE: RE: RunOneWorld.sh

Just a note... if you use the - option to su (e.g. su - jdeb7333), the
login scripts _will_ be read.

--Scotti Whitmire
DeRoyal Industries
Xe SP14.2 (moving to 15), AIX 4.3.3, Oracle 8.1.6
 
RE: RE: RunOneWorld.sh

Larry,
Don't mind the correction at all, but I find your comment
interesting since we have been doing this for quite some time (several
years) on HPUX. Are you sure about this? We have had no problems
executing the Run, End or Rmics scripts this way. Could you give me
more information on this? Is their documentation anywhere regarding
this? (Not trying to be a pain - just trying to learn from my
mistakes).
Thanks,

Lisa G. Stinebuck
Senior Service Delivery Technician
Logical EBOC Cincinnati
513-412-7950 x1021
[email protected]
 
Re: RE: RE: RunOneWorld.sh

MEA CULPA :(
I stand corrected (as per gerd's and scottie's posts).

Just be sure to use the "-" option (which we do in some cron jobs).




Larry Jones
[email protected]
OneWorld B733.1, SP 11.3
HPUX 11, Oracle SE 8.1.6
SandBox: OneWorld XE SP15
 
Re: RE: RE: RunOneWorld.sh

Hi eveybody,

Thank you for your answers, but I habe checked the IPC with all values..and the problem persists. Now I have a jde_xxx.log and appears the following error:
Wed May 16 16:29:14 2001 ipcpub1934
process 20892 <jdenet_k> registered in entry 1

20892 Wed May 16 16:29:15 2001 sc_dsptc140
INITIALIZING SCHEDULER SERVER KERNEL

20892 Wed May 16 16:29:15 2001 sc_dsptc163
Attempting to auto-start the Scheduler.

20892 Wed May 16 16:29:19 2001 sc_dsptc841
Failed to fetch the Scheduler Server host name from the F98611. The Sch
eduler Server's Logical Data Source is . Could not validate the Scheduler Name.

20892 Wed May 16 16:29:19 2001 sc_dsptc860
Scheduler does not run on this machine. The real Scheduler Server is .

20892 Wed May 16 16:29:19 2001 sc_dsptc195
This server will not start the Scheduler.

Anybody know this error?, Have I got to configure the Scheduler in OneWorld?, any suggestion?.
Thanks again.
 
Re: RE: RE: RunOneWorld.sh

Hi eveybody,

Thank you for your answers, but I have checked the IPC with all values..and the problem persists. Now I have a jde_xxx.log and appears the following error:
Wed May 16 16:29:14 2001 ipcpub1934
process 20892 <jdenet_k> registered in entry 1

20892 Wed May 16 16:29:15 2001 sc_dsptc140
INITIALIZING SCHEDULER SERVER KERNEL

20892 Wed May 16 16:29:15 2001 sc_dsptc163
Attempting to auto-start the Scheduler.

20892 Wed May 16 16:29:19 2001 sc_dsptc841
Failed to fetch the Scheduler Server host name from the F98611. The Sch
eduler Server's Logical Data Source is . Could not validate the Scheduler Name.

20892 Wed May 16 16:29:19 2001 sc_dsptc860
Scheduler does not run on this machine. The real Scheduler Server is .

20892 Wed May 16 16:29:19 2001 sc_dsptc195
This server will not start the Scheduler.

Anybody know this error?, Have I got to configure the Scheduler in OneWorld?, any suggestion?.
Thanks again.
 
RE: RE: RE: RunOneWorld.sh

Larry,
Thanks - you scared me there for a minute!! Yes, we do use the '-'
option when switching users and doing so invokes all of the environment
variables for that user. We could have avoided this thread
all-together if I had included the '-' as I should have.
Thanks,

Lisa G. Stinebuck
Senior Service Delivery Technician
Logical EBOC Cincinnati
513-412-7950 x1021
[email protected]
 
Back
Top