About Process Scheduler in PS

Hi one and all what is process scheduler in PS ?
My major question is What is the difference b/w Process Monitor and Report Manager Under Process Scheduler ??

Hi,
Read this in Peoplebooks to learn more about the process scheduler.
Process Scheduler, Process Monitor and Report Manager:
http://docs.oracle.com/cd/E28394_01/pt852pbh1/eng/psbooks/tprs/book.htm?File=tprs/htm/tprs02.htm#H2001
Process Monitor
After you submit a job using the Process Scheduler Request page, use Process Monitor to review the status of scheduled or running processes. You can view all processes to see the status of any job in the queue and control processes that you initiated. Process Monitor consists of two pages: the Process List page and the Server List page.
Use the Process List page to monitor the process requests that you submit. If a process encounters an error, or if a server is down, you can find out almost immediately. You can also see what processes are queued to run in the future.
Report Manager
As part of PeopleSoft Process Scheduler, Report Manager provides several different methods of viewing reports, based on the level of access granted. For example, only users who are assigned to a Report Manager Administration role in PeopleSoft Security can delete reports from the database using the Report Manager - Administration page.
Using Report Manager, you can see all of the reports that you are authorized to view by opening your report list in a browser. Folders are provided to assist in organizing reports and reducing the size of the report lists.
This is the difference between the two.
Regards,
Wijnand

Similar Messages

Where is Process scheduler

Hi,
where can I see on which machine is installed Process scheduler ?
Yes on Web interface (4 tiers) in process monitor it is indicated but for the moment it is wrong !! I looked for it in psappsrv.cfg but did not find.
Is there any table other than PS_SERVERDEFN can have it ?
Thank for help.

psappsrv.cfg is the Application server configuration file, nothing about process scheduler there.
in process monitor it is indicated but for the moment it is wrong What is wrong ? There are always some default process scheduler created.
Nicolas.

Error Start Process Scheduler after configure Crystal Path

Hi All,
Kindly help me to solve this issue. I'd installed Peoplesoft HCM 9.2, Application Server and Process Scheduler run sucessfull but after i install Crystal Report Runtime Redistribute 2008 and configure crystal path (C:\Program Files(x86)\Business Objects\BusinessObjects Enterprise 12.0\win32_x86) i got this error when i try to start process scheduler
Booting admin processes ...
exec BBL -A :
process id=3164 ... started
1 process started
Attaching to active bulletin board.
> Attempting to boot ...
INFO: Oracle Tuxedo, Version 11.1.1.2.0 with VS2010, 64-bit, Patch Level (none)
Booting server processes ...
exec PSMSTPRC -0 ".\LOGS\stdout" -e ".\LOGS\stderr" -A -- -CD ORCL -PS PSNT -A start -S PSMSTPRC :
CMDTUX_CAT:1685: ERROR: Application initialization failure
CMDTUX_CAT:827: ERROR: Fatal error encountered; initiating user error handler
tmshutdown -qy

Hi all,
I am getting a similar message ...
failure: CORE3170: Configuration initialization failed: Error running init function load-modules: dlopen of /opt/SUNWwbsvr/plugins/passthrough/libpassthrough.so failed (ld.so.1: webservd: fatal: /opt/SUNWwbsvr/plugins/passthrough/libpassthrough.so: wrong ELF class: ELFCLASS64)
+/usr/bin/isainfo -kv+ gives *64-bit sparcv9 kernel modules*
I have also added the path of libpassthrough.so in LD_LIBRARY_PATH .
What can be the reason now ?
I had downloaded SP4. Does my webserver(sunone 6.1) also needs an update of service pack 4 then ? (It was installed about 2 months ago).

App server , process scheduler , web server and DB scripts

Team,
Good Morning.
I am looking for the script which will help me in doing health check-up for app server , process scheduler , web server and DB.
The script should trigger a email when any one of the domain is down and when it get up.
Waiting heartly

If you really only want scripts you should write them yourself. If you don't understand the script how can you be expected to support it, modify it, or add new features? You don't even indicate what OS your using? I could give you a copy of a powershell script but what good is that on a linux box?
You need to identify what you really are interested in monitoring. Is it process health only? actual system integrity? Do you need to know if a process count goes under a certain threshold? Is the processes scheduler really working? Is queuing occurring somewhere? Is the web server at a critical number of open sessions? log monitoring for keywords? Do you need to actually simulate a web session which would prove the full system is working in one execution, although it won't indicate a failure will occur where some other monitoring might?
This is why the others have recommended pre-built packages that already offer most of this. If you still want scripts, gather your requirements, think about what you really need, try some stuff on your own, and if you have a specific problem with a script or how to accomplish a particular system check, post a new question, and I'll do my best to help. I think you'll get a better response from everyone if you do that.

Process Scheduler start very slowly

Hi,
Fscm90, tools 8.50 on Win 2003 DB Oracle 10 g
PS takes about one hour to start :
from Tuxedo log
113150.MYSERVER!BBL.5624.2452.0: 10-29-2010: Tuxedo Version 10.3.0.0 with VS2005, 32-bit, Patch Level (none)
113150.MYSERVER!BBL.5624.2452.0: LIBTUX_CAT:262: INFO: Standard main starting
113152.MYSERVER!PSMSTPRC.7128.7648.-2: 10-29-2010: Tuxedo Version 10.3.0.0 with VS2005, 32-bit
113152.MYSERVER!PSMSTPRC.7128.7648.-2: LIBTUX_CAT:262: INFO: Standard main starting
113202.MYSERVER!PSDSTSRV.7844.2476.0: 10-29-2010: Tuxedo Version 10.3.0.0 with VS2005, 32-bit
113202.MYSERVER!PSDSTSRV.7844.2476.0: LIBTUX_CAT:262: INFO: Standard main starting
113206.MYSERVER!PSPRCSRV.628.6844.-2: 10-29-2010: Tuxedo Version 10.3.0.0 with VS2005, 32-bit
113206.MYSERVER!PSPRCSRV.628.6844.-2: LIBTUX_CAT:262: INFO: Standard main starting
124223.MYSERVER!PSMONITORSRV.2032.8068.-2: 10-29-2010: Tuxedo Version 10.3.0.0 with VS2005, 32-bit
124223.MYSERVER!PSMONITORSRV.2032.8068.-2: LIBTUX_CAT:262: INFO: Standard main startingAnd :
From Schedul log :
PSPRCSRV.628 (0) [10/29/10 11:32:08 VP1@MYSERVER](0)    Log Fence is set to 3 = Display detailed message
PSPRCSRV.628 (0) [10/29/10 11:32:08 VP1@MYSERVER](3) Validating Application Engine Server Setup....
PSPRCSRV.628 (0) [10/29/10 11:32:08 VP1@MYSERVER](3)       Processes with Generic Process Type of Application Engine:
PSPRCSRV.628 (0) [10/29/10 11:32:08 VP1@MYSERVER](3)                XML Publisher            :    3
PSPRCSRV.628 (0) [10/29/10 11:32:08 VP1@MYSERVER](3)                Optimization Engine      :    2
PSPRCSRV.628 (0) [10/29/10 11:32:08 VP1@MYSERVER](3)                Total:                        5
PSPRCSRV.628 (0) [10/29/10 11:32:08 VP1@MYSERVER](3)    CPU Threshold Setting : 0 percent
PSPRCSRV.628 (0) [10/29/10 11:32:08 VP1@MYSERVER](3)    Memory Threshold Setting : 0 percent
PSPRCSRV.628 (0) [10/29/10 12:42:22 VP1@MYSERVER](3)   Process Scheduler Server PSNT running in remote mode
PSPRCSRV.628 (0) [10/29/10 12:42:22 VP1@MYSERVER](3) Process Scheduler Server PSNT registered
PSPRCSRV.628 (0) [10/29/10 12:42:22 VP1@MYSERVER](3)    Server action mode: Initializing
PSPRCSRV.628 (0) [10/29/10 12:42:22 VP1@MYSERVER](2)   PSDaemon disabled
PSPRCSRV.628 (0) [10/29/10 12:42:22 VP1@MYSERVER](3)    Checking Process cancels...
PSPRCSRV.628 (0) [10/29/10 12:42:22 VP1@MYSERVER](0)    Server Initialization Complete
PSPRCSRV.628 (0) [10/29/10 12:42:22 VP1@MYSERVER](0) Server started
PSPRCSRV.628 (0) [10/29/10 12:42:37 VP1@MYSERVER](3)    Server: PSNT checking status...No probleme on database. No user connected yet.
Can not understand.
Thank for help.

what are the hardware specifications on the server? When application servers and process schedulers run on the same machine, application servers consume more ram on the server to run the application, process schedulers may not had enough memory to run and wait for application servers on that.
Having AS and PS on the same box is not a good design. usually PS is made on the db box (or) AS and PS go separately on different boxes.
if you can move PS onto a different box, ur performance will grow in a big way.
Thanks!

Details about Process chain

Details about Process chain

Hi Vijay,
            Well the major components of Process chain is mentioned as under:-
A process Chain is a sequence of processes in BI system that executes in the Background.
Commonly Used Process Types
1. Start
2. Execute InfoPackage
3. DTP
4. Attribute Change Run
5. Save Hierarchy
6. Delete Index
7. Generate Index
8. Activate DSO data
9. Update DSO data
10. Complete Deletion of Data Target Content
11. Delete Entire Content of Linked Transactional DSO/ODS
12. Initial Fill of New Aggregates
13. Roll up of Filled Aggregates/BIA indexes
14. Compression of InfoCubes
15. Read PSA and Update Data Target
16. AND
17. OR
18. XOR
If you want to include a load process in the process chain, you need to have already created an InfoPackage.
You cannot load flat file data from a client workstation in the background. For this reason, you have stored your data on an application server.
Creating Process Chains
You have the option of creating a process chain in the process chain maintenance screen directly or by using a maintenance dialog for a process:
Creating a Process Chain Directly in the Process Chain Maintenance Screen
You are in the BW Administrator Workbench.
       1.      Click on the Process Chain Maintenance icon in the AWB toolbar.
The Process Chain Selection dialog window appears.
       2.      Choose Create.
       3.      Enter the technical name and a description of the chain, and confirm your entry.
The Add Start Process dialog window appears.
       4.      Create a variant for a start process.
a.       On the Maintain Start Process screen, choose whether you want to schedule the chain directly or whether you want to start it using a metachain.
b.       If you choose to schedule the chain directly, enter the start date value for the chain under Change Selections and save your entries.
The Maintain Start Process screen appears again.
c.       Save your entries, return to the previous screen and confirm your entries in the Add Start Process dialog window.
You are taken to the Plan View of the process chain maintenance screen.
In the left-hand area of the screen, a navigation area is displayed. In the right-hand area of the screen, the process chain is displayed.
       5.      Use the drag-and-drop function to add the relevant processes into your process chain.
You use the Process Types function to select the processes. This sorts the process types according to different categories. You can also call up InfoPackages and processes for the data target from the separate InfoSources and Data Targets navigation trees.
If you insert into the chain a process that is linked to additional processes, the respective process variants are generated and inserted into the process chain automatically. These variants are suggestions and can be changed, replaced or removed from the chain if required.
Only if the attribute realignment run is inserted automatically, do you also arrive at the variant maintenance screen.
If you want to specify yourself the processes that are to be included in a chain, choose Settings ® Default Chains, and select the Do Not Suggest Processes option. As a result, the system does not suggest, generate, or insert automatically any processes into the chain. This setting is user-specific.
If the chain that you create does not correspond to the standard, the system displays a warning. You can ignore these warnings if you are sure that you are creating a chain that meets your requirements. Warnings do not affect how the chain operates during runtime.
Your chain is checked in the checking view and during activation. The system tells you if it discovers any errors.
Creating a Process Chain Using the Maintenance Dialog for a Process
You are in the maintenance dialog of a process that you want to include in a process chain.
       1.      Choose the Process Chain Maintenance pushbutton and create a process variant.
       2.      Save the variant and go back to the previous screen.
A dialog window appears in which you enter a technical name and a description of the chain that you want to create.
       3.      Confirm your entries.
The Add Start Process dialog window appears.
       4.      Create a variant for a start process.
a.       On the Maintain Start Process screen, choose whether you want to schedule the chain directly or whether you want to start it using a metachain.
b.       If you choose to schedule the chain directly, enter the start date value for the chain under Change Selections and save your entries.
The Maintain Start Process screen appears again.
c.       Save your entries, return to the previous screen and confirm your entries in the Add Start Process dialog window.
You are taken to the Plan View of the process chain maintenance screen.
The various process categories, the application processes, and collection processes are displayed in the left-hand area of the screen. In the right-hand area of the screen, the process chain is displayed.
If the process that you used to create a chain is linked to additional processes, the respective process variants are generated and inserted into the process chain automatically. These variants are suggestions and can be changed, replaced or removed from the chain if required.
Only if the attribute realignment run is inserted automatically, do you also arrive at the variant maintenance screen.
If you want to specify yourself the processes that are to be included in a chain, choose Settings ® Default Chains, and select the Do Not Suggest Processes option. As a result, the system does not suggest, generate, or insert automatically any processes into the chain. This setting is user-specific.
If the chain that you create does not correspond to the standard, the system displays a warning. You can ignore these warnings if you are sure that you are creating a chain that meets your requirements. Warnings do not affect how the chain operates during runtime.
Your chain is checked in the checking view and during activation. The system tells you if it discovers any errors.
       5.      Use the drag-and-drop function to insert any additional relevant processes into your process chain.
You use the Process Types function to select the processes. This sorts the process types according to different categories. You can also call up InfoPackages and processes for the data target from the separate InfoSources and Data Targets navigation trees.
Additional Steps to Creating a Process Chain
       6.      When you add a process, you need to select a process variant or create a new variant. For collection processes, the system determines the variants.
Various functions for working with the process are available from the context menu:
Context Menu Entry for a Process
Function Information
Maintain Variants
With the exception of the variants in the collection process, you can use this function to change all process variants.
Exchange Variants
You can swap the variants for an existing variant or a new variant.
Display Scheduled Jobs
Once the process chain is active, you can use this function to display the jobs that have been scheduled.
Display All Jobs
After at least one run of the process chain, you can display, for a specific process, all of the scheduled jobs for this process and all of the jobs with which this process was run. You arrive at the job overview from where you call up the relevant job log.
Create Message
You can also send messages to an application process of the chain, depending on the success or failure of the process.
1.       From the context menu of a process, create an additional process variant of the Send Message type.
2.       If you maintain a message, first specify whether you want the message to be sent when the process has been completed successfully or unsuccessfully. Then choose Next.
3.       You arrive at a window, in which you can select an existing process variant or create a new one.
4.       If you create a new process variant, edit the document that is going to be sent, and maintain a list of recipients.
5.       Save your process variant and go back a step.
The message process variant is now assigned to your application process. When the message is sent, the status information and the process log can also be sent.
Wait Time
You use this function only to debug a process run.
Specify how long (in seconds) you want the delay to be between one event being triggered and the next process starting.
You can capture the process by using transaction SM37 (Job Overview) or SM50 (Process Overview).
Remove Process
You use this function to remove a process from a process chain.
Manage Data Target
You use this function in connection with the following types of process variants
·         constructing indexes
·         deleting indexes
·         constructing database statistics
·         rolling up filled aggregates
·         compressing InfoCubes
·         activating ODS object data
to call up the administration for each of the data targets.
       7.      Hold down the left mouse button to connect the processes through events.
Before you do this, select the process underneath the process type row, and position the cursor over the required process. When you select the process type row, the whole process is moved into the plan view.
From the context menu of a link, you can display the event or remove the link again. To do this, highlight the link and right-click with the mouse.
       8.      If necessary, specify whether you want the event to be triggered after the previous process has been completed successfully or unsuccessfully or whether you want the event to be triggered independently of the outcome of the process that precedes it.
       9.      Under Attributes ®Display Components assign a display component to the process chain.
   10.      Maintain additional process chain attributes if necessary.
   11.      Check your process chain in the Check View and make any necessary corrections.
The Legend explains the meaning of the different colors used to display the processes and links.
From the context menu for a process, you can display the messages resulting from the check.
   12.      Save your process chain if it does not contain any errors.
Result
Your process chain can be activated. After activation, the chain starts in accordance with the start process selections. For example, if you scheduled the start process directly and chose Immediately as the start date value, the chain run starts immediately after activation. In the Log View, you can display the reports for the chain runs.

Component is not getting displayed in process scheduler menu

Hi All,
I have created a project and created/registered a component in that project. I have also added a page which is having a record definition with a record named L_RUNCNTL having two search fields, to this component and configured L_RUNCNTL as search record for this component.
I have registered this component with below details:
Menu Name : PROCESS_SCHEDULER
Bar Name : PROCESS
Folder Name as PT_PROCESS_SCHEDULER
Select “Always Use default local node?” Check box
Permission List : PTPT1000
But after registration, when I open process scheduler menu I dont see this component listed. However, previously I created a component in this project and registered it with same details given above and I could see it in process scheduler menu.
I am surprised why another component registered with same details is not getting displayed in process scheduler menu.

Thanks Michel,
I got this problem resolved. Here is what I did:
Ran portal security sync at the navigation PeopleTools > Portal > Portal Security Sync.
Cleared browser cache, accessed the page again and saw the link was available.

How to print of a crystal output on paper through process Scheduler in PeopleSoft.

Post Author: rajaumareddy
CA Forum: Charts and Graphs
while printing crystal through process scheduler in PeopleSoft it giving Error as Runstatus. and i given in Printer destination.
Could u help me to find solution.
1. what are process scheduler setup.
2. Is there any Sever side setup (Default server)

Srinivas, Thanks for your quick reply.
This is smartform, and sending the output as pdf, except the the first page on which I have the text to be printed on the email body. In this email body text I have to display an email.
when user clicks on the email should open an outlook with the email id in the TO. Hope this helps.
Thank you,
Surya

Error in creating the process scheduler

Hi all,
I recently installed with Peolesoft 8.9 and tools 8.49 and oracle 9i.
Now i tried to create the process scheduler.
I have got the error in the image http://narchu.coolinc.info/install_failed.html
what i did.
from the menu i selected to create a new process scheduler.
gave the name as fsdmo
configure? yes
changed the username to VP1
changed the password to VP1
and then load the config as shown.
start the process scheduler.
then it gave the error in the image in the above link.
The password is not gettin encrypted. i think it must be encrypted, but i am not sure.
Can any one please help solving it.
Thank you,
Bye.

I think if it is default installation without screwing anything VP1 can start app and Proc server.
But Nicolas is right, to get more we need log file....it may be database connectivity issue, password encryption issue , tuxedo issue and much more.If u can post the logs it will helpful to diagnose your issue.

I am getting the below error while bringing up the Process Scheduler error

Hello ,
I am getting the below error while bringing up the Prcs Scheduler.
Cannot open message catalog TMADMIN_CAT
Starting Process Scheduler Server PSNT for Database FSUAT ...
NLS:4: Cannot open message catalog CMDTUX_CAT, set 1, num 752; check TUXDIR=C:\b
ea\Tuxedo8.1, LANG=English_United States.1252
INFO: BEA Tuxedo, Version 8.1, 32-bit, Patch Level 192
NLS:4: Cannot open message catalog LIBTUX_CAT, set 1, num 1571; check TUXDIR=C:\
bea\Tuxedo8.1, LANG=English_United States.1252
NLS:4: Cannot open message catalog LIBTUX_CAT, set 1, num 1570; check TUXDIR=C:\
bea\Tuxedo8.1, LANG=English_United States.1252
NLS:4: Cannot open message catalog CMDTUX_CAT, set 1, num 793; check TUXDIR=C:\b
ea\Tuxedo8.1, LANG=English_United States.1252
exec BBL -A :
NLS:4: Cannot open message catalog CMDTUX_CAT, set 1, num 820; check TUX
DIR=C:\bea\Tuxedo8.1, LANG=English_United States.1252
NLS:4: Cannot open message catalog CMDTUX_CAT, set 1, num 801; check TUXDIR=C:\b
ea\Tuxedo8.1, LANG=English_United States.1252
exec PSDSTSRV -p 1,600:1,1 -sPostReport -- -C psprcs.cfg -CD FSUAT -PS PSNT -A s
tart -S PSDSTSRV :
NLS:4: Cannot open message catalog CMDTUX_CAT, set 1, num 1685; check TU
XDIR=C:\bea\Tuxedo8.1, LANG=English_United States.1252
tmboot: NLS:4: Cannot open message catalog CMDTUX_CAT, set 1, num 827; check TUX
DIR=C:\bea\Tuxedo8.1, LANG=English_United States.1252
tmshutdown -y
NLS:4: Cannot open message catalog CMDTUX_CAT, set 1, num 753; check TUXDIR=C:\b
ea\Tuxedo8.1, LANG=English_United States.1252
NLS:4: Cannot open message catalog CMDTUX_CAT, set 1, num 916; check TUXDIR=C:\b
ea\Tuxedo8.1, LANG=English_United States.1252
NLS:4: Cannot open message catalog CMDTUX_CAT, set 1, num 907; check TUXDIR=C:\b
ea\Tuxedo8.1, LANG=English_United States.1252
NLS:4: Cannot open message catalog CMDTUX_CAT, set 1, num 936; check TUXDIR=C:\b
ea\Tuxedo8.1, LANG=English_United States.1252
NLS:4: Cannot open message catalog CMDTUX_CAT, set 1, num 948; check TUXDIR=C:\b
ea\Tuxedo8.1, LANG=English_United States.1252
NLS:4: Cannot open message catalog CMDTUX_CAT, set 1, num 775; check TUXDIR=C:\b
ea\Tuxedo8.1, LANG=English_United States.1252
Please suggest.

Duplicate thread :
Re: I am getting the attached error while bringing up the Prcs Scheduler
Nicolas.

Getting error while posting reports on Unix Process Scheduler Server

Hello ,
I am getting the below error while posting reports on Unix Process Scheduler Server .
PSDSTSRV.14338 (2) [09/08/09 08:21:34 PostReport](1) (JNIUTIL): Java exception thrown: java.io.IOException: Stream closed.
PSDSTSRV.14338 (2) [09/08/09 08:21:34 PostReport](3) HTTP transfer error.
PSDSTSRV.14338 (2) [09/08/09 08:21:34 PostReport](3) Post Report Elapsed Time: 0.0900
PSDSTSRV.14171 (10) [09/08/09 08:21:34 PostReport](1) (JNIUTIL): Java exception thrown: java.io.IOException: Stream closed.
Please advise ,thank you.

user5838027 wrote:
Node name :PS_HTTP
URL: http://ddas1020.dev.com:16000/psreports/hrdmo
URI:SchedulerTransfer/hr90dmo
URI Port: 16000
Please let me know if any other info is needed.
Thanks.
typo...
URL: http://ddas1020.dev.com:16000/psreports/hr90dmo
Hopefully, your application URL looks like http://ddas1020.dev.com:16000/psp/hr90dmo/..., your URI host looks like ddas1020.dev.com (or corresponding ip address), and hhtp is checked.
Did you also tried to give the web login/password ?
Nicolas.

I would like to inquire about the schedule that is synchronized to iCal in CalDav protocol from our system. Schedule that is synchronized could be edited from the iPad or iPhone terminal, but I can no longer edit from iOS5.1. Can you tell me some tips?

I would like to inquire about the schedule that is synchronized to iCal in CalDav protocol from our system. Schedule that is synchronized could be edited from the iPad or iPhone terminal, but I can no longer edit from iOS5.1. We did not fix anything program itself, but the data format to be synchronized is the same. Can you tell me some tips?

I would like to inquire about the schedule that is synchronized to iCal in CalDav protocol from our system. Schedule that is synchronized could be edited from the iPad or iPhone terminal, but I can no longer edit from iOS5.1. We did not fix anything program itself, but the data format to be synchronized is the same. Can you tell me some tips?

Process scheduler picking up trace settings that are not currently on

I'm running a custom application engine program. I tested the program in the same instance last week with a full trace turned on. The trace was turned on under processes. I've since refreshed the database and dumped the process scheduler cache (Unix process scheduler). After the refresh, I turned off the process trace. I ran a quick test of the program to see what the trace settings are. To my disappointment the full trace is still showing at the end of my parameters list in the process monitor. I've tried forcing a trace -0, the parameters will not change. It's very, very strange. Unforuntately, I have to process a lot of data using this application engine program using CI. Is there any other area in Peoplesoft that I might be forgetting that an application engine trace can be turned on?

How have you refreshed the database ? How did you re-apply your customization after refresh ? How is defined the prcs ? Did you change the prcs configuration file to set the trace off ? Did you checked the process definition ?
Nicolas.

App Server and Process Scheduler stuck while booting

Hi All,
We are facing a big issue in our production instance.The application server showed down while accessing the PIA.When we tried to reboot the same it didnt start and was getting stuck after some steps..few snipets are below after the last PSSRENSRV process does not proceed further.
exec PSSAMSRV --A -- -C psappsrv.cfg -D FNPROD -S PSSAMSRV:
        CMDTUX_CAT:819: INFO:Process id=5584 Assume started <pipe>.
exec PSSAMSRV --A -- -C psappsrv.cfg -D FNPROD -S PSSAMSRV:
        CMDTUX_CAT:819: INFO:Process id=5600 Assume started <pipe>.
exec PSSAMSRV --A -- -C psappsrv.cfg -D FNPROD -S PSSAMSRV:
        CMDTUX_CAT:819: INFO:Process id=5616 Assume started <pipe>.
exec PSSAMSRV --A -- -C psappsrv.cfg -D FNPROD -S PSSAMSRV:
        CMDTUX_CAT:819: INFO:Process id=5632 Assume started <pipe>.
exec PSSAMSRV --A -- -C psappsrv.cfg -D FNPROD -S PSSAMSRV:
        CMDTUX_CAT:819: INFO:Process id=5648 Assume started <pipe>.
exec PSSAMSRV --A -- -C psappsrv.cfg -D FNPROD -S PSSAMSRV:
        CMDTUX_CAT:819: INFO:Process id=5664 Assume started <pipe>.
exec PSRENSRV --A --   -C psappsrv.cfg -D FNPROD -S PSRENSRV:The tuxedo,appserv and renserv logs shows,
renserv log
----- Begin booting PSRENSRV -------------------------
0.5608 [14/Jul/2011 07:51:54](ERROR) CRenTuxSvcMgr::ReqBootParameters - Tux service call failed.
----- Begin booting PSRENSRV -------------------------
0.5056 [14/Jul/2011 07:58:47](ERROR) CRenTuxSvcMgr::ReqBootParameters - Tux service call failed.
----- Begin booting PSRENSRV -------------------------
0.780 [14/Jul/2011 08:21:04](ERROR) CRenTuxSvcMgr::ReqBootParameters - Tux service call failed.------------------------------------------------------------------------------------------
tuxedo log
receiving messages, tperrno = TPEOS, Uunixerr = UMSGRCV
082104.UKLO2K3S55!JSH.5060.5084.-2: JOLT_CAT:1107: "ERROR: Error receiving messages, tperrno = TPEOS, Uunixerr = UMSGRCV"
082104.UKLO2K3S55!WSH.4364.1752.0: WSNAT_CAT:1107: ERROR: Error receiving messages, tperrno = TPEOS, Uunixerr = UMSGRCV
082104.UKLO2K3S55!WSH.4472.4416.0: WSNAT_CAT:1107: ERROR: Error receiving messages, tperrno = TPEOS, Uunixerr = UMSGRCV
082104.UKLO2K3S55!WSH.1684.4128.0: WSNAT_CAT:1107: ERROR: Error receiving messages, tperrno = TPEOS, Uunixerr = UMSGRCV
082104.UKLO2K3S55!WSH.4256.4172.0: WSNAT_CAT:1107: ERROR: Error receiving messages, tperrno = TPEOS, Uunixerr = UMSGRCV
082104.UKLO2K3S55!JSH.4876.496.-2: JOLT_CAT:1107: "ERROR: Error receiving messages, tperrno = TPEOS, Uunixerr = UMSGRCV"
082104.UKLO2K3S55!WSH.4896.4284.0: WSNAT_CAT:1107: ERROR: Error receiving messages, tperrno = TPEOS, Uunixerr = UMSGRCV
082104.UKLO2K3S55!JSH.4800.1036.-2: JOLT_CAT:1107: "ERROR: Error receiving messages, tperrno = TPEOS, Uunixerr = UMSGRCV"
082104.UKLO2K3S55!WSL.3904.4032.0: LIBTUX_CAT:703: ERROR: Cannot get statistics on message queue 43
082104.UKLO2K3S55!JSL.4316.4024.0: JOLT_CAT:1196: "INFO: Terminating handlers in preparation for shutdown"
082104.UKLO2K3S55!WSL.3904.4032.0: WSNAT_CAT:1197: INFO: Exiting system
082104.UKLO2K3S55!JREPSVR.5768.5800.0: LIBTUX_CAT:271: ERROR: System lock semop failure, key = 61480 (errno = 22)
082104.UKLO2K3S55!WSL.3904.4032.0: LIBTUX_CAT:268: ERROR: Failed to stop serving
082104.UKLO2K3S55!JSL.4316.4024.0: JOLT_CAT:1197: "INFO: Exiting system"
082104.UKLO2K3S55!JREPSVR.5768.5800.0: LIBTUX_CAT:268: ERROR: Failed to stop serving
082104.UKLO2K3S55!JSL.4316.4024.0: LIBTUX_CAT:268: ERROR: Failed to stop serving
082105.UKLO2K3S55!PSWATCHSRV.6124.568.-2: ERROR: msgrcv err(LIBTUX_CAT:669: ERROR: Message operation failed because of the invalid message queue identifier): errno=22,qid=2,buf=9580216,bytes=4572,type=-1073741824,flag=2048
082105.UKLO2K3S55!PSWATCHSRV.6124.568.-2: LIBTUX_CAT:268: ERROR: Failed to stop serving------------------------------------------------------------------------------------------
app serv log
PSADMIN.4944 (0) [07/14/11 07:48:28](0) Begin boot attempt on domain FNPROD
PSWATCHSRV.4720 (0) [07/14/11 07:48:33] Starting
PSADMIN.4944 (0) [07/14/11 07:52:29](0) End boot attempt on domain FNPROD
PSADMIN.4944 (0) [07/14/11 07:55:46](0) Begin boot attempt on domain FNPROD
PSWATCHSRV.1412 (0) [07/14/11 07:55:50] Starting
PSADMIN.4892 (0) [07/14/11 08:08:07](0) Begin boot attempt on domain FNPROD
PSWATCHSRV.5032 (0) [07/14/11 08:08:13] Starting
PSADMIN.4892 (0) [07/14/11 08:08:27](0) End boot attempt on domain FNPROD
PSADMIN.6104 (0) [07/14/11 08:20:28](0) Begin boot attempt on domain FNPROD
PSWATCHSRV.6124 (0) [07/14/11 08:20:32] Starting-----------------------------------------------------------------------------------------
tuxedo log
213815.UKLO2K3S55!PSSAMSRV.6072.6040.0: LIBTUX_CAT:262: INFO: Standard main starting
213815.UKLO2K3S55!PSRENSRV.2440.2444.-2: 07-13-2011: Tuxedo Version 8.1 32-bit Windows.
213815.UKLO2K3S55!PSRENSRV.2440.2444.-2: LIBTUX_CAT:262: INFO: Standard main starting
214434.UKLO2K3S55!BBL.5964.4464.0: ERROR: msgrcv err(LIBTUX_CAT:666: ERROR: Message operation failed because the queue was removed): errno=100,qid=257,buf=10285048,bytes=4572,type=-1073741824,flag=0
214434.UKLO2K3S55!PSRENSRV.2440.2444.-2: ERROR: msgrcv err(LIBTUX_CAT:666: ERROR: Message operation failed because the queue was removed): errno=100,qid=277,buf=11551960,bytes=8668,type=805306369,flag=0
214434.UKLO2K3S55!BBL.5964.4464.0: ERROR: msgrcv err(LIBTUX_CAT:669: ERROR: Message operation failed because of the invalid message queue identifier): errno=22,qid=257,buf=10285048,bytes=4572,type=0,flag=0
214434.UKLO2K3S55!BBL.5964.4464.0: LIBTUX_CAT:271: ERROR: System lock semop failure, key = 33242 (errno = 22)
214434.UKLO2K3S55!BBL.5964.4464.0: LIBTUX_CAT:268: ERROR: Failed to stop serving
214434.UKLO2K3S55!BBL.5964.4464.0: CMDTUX_CAT:26: INFO: The BBL is exiting system
214434.UKLO2K3S55!PSWATCHSRV.5208.4528.-2: ERROR: msgrcv err(LIBTUX_CAT:669: ERROR: Message operation failed because of the invalid message queue identifier): errno=22,qid=258,buf=9654368,bytes=27996,type=-1073741824,flag=2048
214434.UKLO2K3S55!PSWATCHSRV.5208.4528.-2: LIBTUX_CAT:268: ERROR: Failed to stop serving
214507.UKLO2K3S55!tmboot.4616.5152.-2: 07-13-2011: Tuxedo Version 8.1 32-bit Windows.
214507.UKLO2K3S55!tmboot.4616.5152.-2: TUXNT_CAT:4: ERROR: Cannot access ipc server (The system cannot find the file specified.
214507.UKLO2K3S55!tmboot.4616.5152.-2: tmboot: CMDTUX_CAT:827: ERROR: Fatal error encountered; initiating user error handler
214508.UKLO2K3S55!PSADMIN.868: End boot attempt on domain FNPRODAlso the process scheduler was not getting booted the logs are shown below,
scheduler log
085646.UKLO2K3S55!restartsrv.2484.4116.-2: server BASE/101: CMDTUX_CAT:587: INFO: Cannot restart server, scheduling for cleanup
085653.UKLO2K3S55!BBL.4044.5996.0: LIBTUX_CAT:550: WARN: Cleaning up restartable server BASE/101
085653.UKLO2K3S55!BBL.4044.5996.0: LIBTUX_CAT:216: WARN: Process 4300 died; removing from BB
085653.UKLO2K3S55!BBL.4044.5996.0: LIBTUX_CAT:216: WARN: Process 5372 died; removing from BB
085653.UKLO2K3S55!BBL.4044.5996.0: LIBTUX_CAT:216: WARN: Process 5640 died; removing from BB
085653.UKLO2K3S55!BBL.4044.5996.0: LIBTUX_CAT:216: WARN: Process 5768 died; removing from BB
085653.UKLO2K3S55!cleanupsrv.4148.4364.-2: 07-14-2011: Tuxedo Version 8.1 32-bit Windows.
085653.UKLO2K3S55!cleanupsrv.4148.4364.-2: GP_CAT:1077: ERROR: Unable to open environment file E:\Psoft\PRDAPP\appserv\prcs\FNPROD\psprcsrv.env for reading
085653.UKLO2K3S55!cleanupsrv.4148.4364.-2: LIBTUX_CAT:353: ERROR: Error putting ENVFILE E:\Psoft\PRDAPP\appserv\prcs\FNPROD\psprcsrv.env into environment
085653.UKLO2K3S55!cleanupsrv.4148.4364.-2: server BASE/101: CMDTUX_CAT:551: INFO: server removed
085743.UKLO2K3S55!BBL.4044.5996.0: ERROR: msgrcv err(LIBTUX_CAT:666: ERROR: Message operation failed because the queue was removed): errno=100,qid=80,buf=10304328,bytes=4572,type=-1073741824,flag=0
085743.UKLO2K3S55!BBL.4044.5996.0: ERROR: msgrcv err(LIBTUX_CAT:669: ERROR: Message operation failed because of the invalid message queue identifier): errno=22,qid=80,buf=10304328,bytes=4572,type=-1073741824,flag=0
085743.UKLO2K3S55!BBL.4044.5996.0: LIBTUX_CAT:271: ERROR: System lock semop failure, key = 64479 (errno = 22)
085743.UKLO2K3S55!BBL.4044.5996.0: LIBTUX_CAT:268: ERROR: Failed to stop serving
085743.UKLO2K3S55!BBL.4044.5996.0: CMDTUX_CAT:26: INFO: The BBL is exiting systemIs this a problem with Tuxedo if so what has to be done...Pls help its a bit urgent...
Thanks in advance...

First of all; if a problem is urgent then you should always contact Oracle support instead.
It looks like the domain is corrupt within Tuxedo. You could try to reconfigure the domain so that it will get recreated in Tuxedo. Make sure you have a backup before you do this. To reconfigure the domain simply open a CMD box and type the following command (from the appserver directory):
psadmin -c configure -d "DOMAIN_NAME"
You can only use this command for the application server.

Issue with Bulk Load Post Process Scheduled Task

Hello,
I successfully loaded users in OIM using the bulk load utility. I also have LDAP sync ON. The documentation says to run the Bulk Load Post Process scheduled task to push the loaded users in OIM into LDAP.
This works if we run the Bulk Load Post Process Scheduled Task right away after the run the bulk load.
If some time had passed and we go back to run the Bulk Load Post Process Scheduled Task, some of the users loaded through the bulk load utility are not created in our LDAP system. This created an off-sync situation between OIM and our LDAP.
I tried to use the usr_key as a parameter to the Bulk Load Post Process Scheduled Task without success.
Is there a way to force the re-evaluation of these users so they would get created in LDAP?
Thanks
Khanh

The scheduled task carries out post-processing activities on the users imported through the bulk load utility.

About Process Scheduler in PS

Similar Messages

Maybe you are looking for