NT PRCS Scheduler

Hi All,
I have recently configured PSNT Prcs Scheduler in new Windows 2008 server machine.
Peopletools 8.46.17
Application HRMS 8.9 release
I'm able to start and stop the prcs scheduler server and its properly displaying server status in PIA(Whether its running or down).
When attempting to run a SQR process from the Process Scheduler, the following error occurs and is reported in the SQR *.out file.
However, when the same Pssqr Command Line is run from a DOS window, the error does not occur and the SQR program runs successfully.
Error:
(SQR 5528) ORACLE OCISessionBegin(RDBMS) error 1017 in cursor 0:
ORA-01017: invalid username/password; logon denied
(SQR 4701) Cannot logon to the database.
SQR for PeopleSoft: Program Aborting.
I have run application engine and it went to success posted status.
Please help me to resolve SQR error.
Regards
Snowy

I do not think Peopletools 8.46 has ever been supported on Windows 2008. Have you checked it out within the support ?
That said, your issue is (very) similar to this one :
*E-SQR: On Windows 2008 Pssqr Errors With SQR 5528, 4701 Or 1803 And ORA-01017 [ID 1100832.1]*+
Basically, the solution is to put it back on Windows 2003.
Nicolas.

Similar Messages

  • I am getting the attached error while bringing up the Prcs Scheduler

    I am getting the attached 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 advise, thank you

    Is that ever running ? Where/how did you installed tuxedo ? Which OS user was used for tuxedo install ?
    Nicolas.

  • 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.

  • Guidelines on Hardware requirements for PeopleSoft 9.2 / 8.53

    Hi-
    Customer is looking for a realistic numbers or guide lines or sample sizes which can be used as a basis for hardware requirements estimation.
    Details like
    Total IOPS requirements for system
    no of SQL transaction issued per min by light, medium and heavy weight users
    CPU & Memory requirement in app server per user
    CPU & Memory requirement in web server per user
    CPU & Memory requirement in prcs scheduler server per user
    CPU & Memory requirement in Database (oracle) per user (tpmc requirements for the same sample set)
    I couldn't find any document which has any of these information.
    Regards,
    DMAC

    Nicolas-
    I have seen the previous thread, as it was for 9.1 thought if we have any updated documents for Application 9.2 with the latest tools 8.53, we are planning for the upgrade and want to build the new hardware, Just want to make sure we have good hardware resources in place before starting the upgrade process.
    Regards,
    DMAC

  • ICWCinternal server error:with some BP records I am getting the below error

    Hi
    When I am searching for some BP records(in ICWC) I am getting the below error
    500 SAP Internal Server Error
    Error message: Type group was changed at runtime. ( type of termination: RABAX_STATE )
    but with some records search is working successfully(some times I'm not getting the above error)
    Have any idea, regarding the above problem
    Thanks in advance
    Warm regards
    bms

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

  • Application Engine hangs

    Hi
    I find that for some reason only programs of type Application Engine are going into queued status.
    All the other programs are running fine.
    The Process scheduler processes application engine programs only after cancelling all application engine programs in queued status
    Can you please let me know what possible causes could be attributed to this behaviour

    Cyril
    As Nick told, find for earlier AE's that are in error/delete and clean them up from Prcs monitor. then,
    *Option1
    Reconfigure the prcs scheduler, clear cache and restart back. Check the last one that is in Queued. If it picks UP then let the backlog clears until u trigger a new one.
    *Option2
    Reconfigure the Prcs Scheduler by selecting 'n' to disable the PSAESRV's, then clear cache and start back.
    IN either case you can try increase the logfence in psprcs.cfg so that it gives detailed info in the logs. btw Wat is the Max concurrency set on AE's? is the issue on both NT/UNX?? (or) Just one of them?
    vKing.

  • PeopleSoft Reports Distribution status is 'Posting'

    In our Peoplesoft application, all the jobs are holding with distribution status as 'Posting'. All the instances are qued up in ps_cdm_transfer table. Once the Process Scheduler server is rebooted, all of them gets posted but again it is holded with posting status. It requires to restart the process scheduler server again and again to get them posted. The instance was working fine till now and none of the logs tells anything about this. Also one point needs to be mentioned here that we are not able to see the message log for the jobs which are holding in 'Posting' status and even though the transfer retries are set, it is not doing the transfer at all. Any help is really appreciated as this is a bit urgent from our end.

    - is there sufficient space on the report Repository?
    - How many DST Agents are there. is spawning enabld?
    - and then check the count(*) from PSPRCSRQST, PSPRCSQUE & PS_CDM_LIST. They should be in Sync.
    Finally check the oldest one that is in 'POSTING' and see how big is its o/p file size. Go to log_output on the Prcs Server. If it is too huge verify wiht users and delete that report and then bounce/reconfigure the Prcs Srv. Mostly this shud resolve the issue.
    and it would be good if u post the info from the Dst & Scheduler logs from Prcs Scheduler.
    -vKing.!

  • Guidelines on Hardware requirements/sizing for PeopleSoft 9.1

    Hello experts
    Customer is looking for a realistic numbers or guide lines or sample sizes which can be used as a basis for hardware requirements estimation.
    For eg HCM with NA payroll, epay,ecompensation, Absense management, eDevelopment, Time & labour
    Same size of 20,000 total users and 2000 concurrent users
    Details like
    Total IOPS requirements for system
    no of SQL transaction issued per min by light, medium and heavy weight users
    CPU & Memory requirement in app server per user
    CPU & Memory requirement in web server per user
    CPU & Memory requirement in prcs scheduler server per user
    CPU & Memory requirement in Database (oracle) per user (tpmc requirements for the same sample set)
    I couldn't find any document which has any of these information.
    Have already checked out 1523278.1 ( which is having minimal requirement for an PeopleSoft setup )

    A lot of work in perspective :
    PeopleTools Performance Guidelines White Paper [ID 747389.1]
    http://www.oracle.com/ocom/groups/public/@otn/documents/webcontent/170237.pdf
    http://www.oracle.com/us/solutions/benchmark/apps-benchmark/peoplesoft-167486.html
    And few more links over there
    http://www.oracle.com/us/products/applications/peoplesoft-enterprise/ptools-resource-library/054014.html
    Nicolas.

  • Scheduling Date issue in Assemble to Order Scenario

    Hi Friends,
    I am facing a Weird issue with Production order Scheduled dates created automatically after creation of Sales Order for configurable material.
    Our availability check is set to check  open Purchase orders, for one component the delivery date in the PO is 20.12.2011, currently at the time of creation of SO the availability check shows this component as a missing part and committed date as 20.12.2011.
    Now the issue is that for one type of customers when the SO is saved, the production order gets created with basic start and finish date of 20.12.2011 with a status CRTD PRC MACM SETC.
    But with another customer group it creates the Production order with today's date basic start and finish date, with a status CRTD MSPT PRC  SETC.
    Now since in both the cases the Material is same and also the components are exactly the same, the only difference is the customer, I am unable to make out why it is happening.
    I am basically a MM  Consultant so am unaware if there is any standard setting relating to customer or something relating to that which is causing such  a issue in scheduling date of the Production Order.
    Regards
    Chandra Shekhar

    Hi Vivek,
    Yes, the availability check is working in both the cases, when I create the sales order, I key in the Configurable material code, then do the configuration, after that system does availability check, in both the cases the result of availability check is same with one component marked as a missing part, available date as 20.12.2011.
    One more thing if I try to view the Production order at the time of SO creation before saving it, the Production order shows today's date, but when I save the SO, and do Credit release, the actual Production order gives different scheduling date based on customer. Just wondering what could be affecting based on Customer, is there any other field present in Customer master which could alter the date.
    I also saw today's scheduling note in some of the cases, but its not coming up in all of the orders created with today's date and moreover the same components are getting scheduled for 20.12.2011 also for diff customer.
    I am afraid I can't provide any screenshots for this as am not permitted to publish any screenshots of the client.
    Regards
    Chandra Shekhar

  • 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.

  • Peoplesoft Master process scheduler PSMSTPRC

    Hi,
    We have PSMSTPRC active on the PSUNX server in prod, i noticed that the psmstprc service is active on the Unix server
    Prog Name Queue Name Grp Name ID RqDone Load Done Current Service--------- ---------- -------- -- ------ --------- ---------------
    BBL 45761 skpkpsf+ 0 53981 2699050 ( IDLE )
    PSMONITORSRV MONITOR MONITOR 1 0 0 ( IDLE )
    PSPRCSRV SCHEDQ BASE 101 0 0 ( IDLE )
    **PSMSTPRC MSTRSCHQ BASE 102 0 0 ( IDLE )**
    PSDSTSRV DSTQ BASE 103 24596 1229800 ( IDLE )
    whereas while i checked the PIA online - process monitor - server list - It says N for PSUNX as MASTER.....
    I can reboot the process scheduler to fix the issue for now... but would like to understand if someone else has come across this and why does it happen
    Peoplesoft - 8.50.09 / DB oracle - 11.1.0.7 / tux - 10.3.0.0 / OS - AIX ...
    Please revert thanks....

    how many prcs do u have.
    lets say, u have 3 process schedulers. one on unix and two on windows. all 3 are configured to be master schedulers. master scheduler shows "Y" to the one which ever comes online first. rest are backup master schedulers. in case your first MS drops, second in line MS becomes "Y"
    Say u have only one scheduler, this shows either your config has been corrupted.check ur OS if this is certified platform for all the products installed.
    try to delete the scheduler completely and redo the scheduler from scratch. do not copy anything from the previous files.
    Thanks

  • Process scheduler

    Hi,
    I created and configured process scheduler through psadmin.exe and getting error when tried to start it......
    PeopleSoft Process Scheduler Administration
    1) Start a Process Scheduler Server
    2) Stop a Process Scheduler Server
    3) Configure a Process Scheduler Server
    4) Create a Process Scheduler Server Configuration
    5) Delete a Process Scheduler Server Configuration
    6) Edit a Process Scheduler Configuration File
    7) Import an existing Process Scheduler Configuration
    8) Show Status of a Process Scheduler Server
    9) Kill a Process Scheduler Server
    10) Clean IPC resources of a Process Scheduler Domain
    q) Quit
    Command to execute (1-10, q) : 1
    Database list:
    1) HC
    Select item number to start: 1
    No Archive subdirectory, creating it...
    No psprcs.cfg in the Archive subdirectory, creating it...
    Installing PeopleSoft ODBC driver and Crystal libraries ...
    PeopleSoft ODBC Driver installed.
    Registering nVision...
    PeopleSoft nVision registered.
    Starting Process Scheduler Server PSNT for Database HC ...
    Booting all admin and server processes in C:\PT8.49\appserv\prcs\HC\PSTUXCFG
    INFO: BEA Tuxedo, Version 9.1, 32-bit, Patch Level 036
    INFO: Serial #: 650522264137-2065448083901, Expiration NONE, Maxusers 1000000
    INFO: Licensed to: Oracle-Peoplesoft-ISV
    Booting admin processes ...
    exec BBL -A :
    process id=3280 ... Started.
    Booting server processes ...
    exec PSMSTPRC -A -- -C psprcs.cfg -CD HC -PS PSNT -A start -S PSMSTPRC :
    CMDTUX_CAT:1685: ERROR: Application initialization failure
    tmboot: CMDTUX_CAT:827: ERROR: Fatal error encountered; initiating user error ha
    ndler
    tmshutdown -y
    Shutting down all admin and server processes in C:\PT8.49\appserv\prcs\HC\PSTUXC
    FG
    Shutting down server processes ...
    Shutting down admin processes ...
    Server Id = 0 Group Id = VIPUL-187A83D08 Machine = VIPUL-187A83D08:
    shutdown succeeded
    1 process stopped.
    thanks in advance
    Vipul

    PT = 8.49
    OS = Win 2003
    Logs under "%PS_HOME%/appserv/prcs/HC directory"
    *1)- file name = MSTRSCHDLR_1207.LOG*
    PSMSTPRC.2388 (0) [12/07/09 18:23:45](0) PeopleTools Release 8.49 (WinX86) starting
    PSMSTPRC.2388 (0) [12/07/09 18:23:45](0) Cache Directory being used: C:\PT8.49\appserv\prcs\HC\CACHE\CACHE\PSMSTPRC_102\
    PSMSTPRC.2388 (0) [12/07/09 18:23:45](0) Server failed to start
    *2)- file name = TUXLOG.120709*
    181957.VIPUL-187A83D08!tmloadcf.3912.1200.-2: 12-07-2009: Tuxedo Version 9.1, 32-bit
    181957.VIPUL-187A83D08!tmloadcf.3912.1200.-2: CMDTUX_CAT:879: INFO: A new file system has been created. (size = 880 512-byte blocks)
    182003.VIPUL-187A83D08!tmloadcf.3912.1200.-2: CMDTUX_CAT:871: INFO: TUXCONFIG file C:\PT8.49\appserv\prcs\HC\PSTUXCFG has been created
    182246.VIPUL-187A83D08!tmloadcf.3536.2376.-2: 12-07-2009: Tuxedo Version 9.1, 32-bit
    182246.VIPUL-187A83D08!tmloadcf.3536.2376.-2: CMDTUX_CAT:879: INFO: A new file system has been created. (size = 880 512-byte blocks)
    182252.VIPUL-187A83D08!tmloadcf.3536.2376.-2: CMDTUX_CAT:871: INFO: TUXCONFIG file C:\PT8.49\appserv\prcs\HC\PSTUXCFG has been created
    182345.VIPUL-187A83D08!BBL.2052.3804.0: 12-07-2009: Tuxedo Version 9.1, 32-bit, Patch Level 036
    182345.VIPUL-187A83D08!BBL.2052.3804.0: LIBTUX_CAT:262: INFO: Standard main starting
    182345.VIPUL-187A83D08!PSMSTPRC.2388.892.-2: 12-07-2009: Tuxedo Version 9.1, 32-bit
    182345.VIPUL-187A83D08!PSMSTPRC.2388.892.-2: LIBTUX_CAT:262: INFO: Standard main starting
    182345.VIPUL-187A83D08!PSMSTPRC.2388.892.-2: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
    182345.VIPUL-187A83D08!tmboot.2556.3812.-2: 12-07-2009: Tuxedo Version 9.1, 32-bit
    182345.VIPUL-187A83D08!tmboot.2556.3812.-2: tmboot: CMDTUX_CAT:827: ERROR: Fatal error encountered; initiating user error handler
    182348.VIPUL-187A83D08!BBL.2052.3804.0: CMDTUX_CAT:26: INFO: The BBL is exiting system
    File name = PSPRCS.CFG
    [Startup]
    ;=========================================================================
    ; Database Signon settings
    ;=========================================================================
    DBName=HC
    DBType=MICROSFT
    UserId=PS
    UserPswd=sxaYMM0Crai26F3R14m0+JWdoXJsSHVovUxlKDaxFDM=
    ConnectId=people
    ConnectPswd=kyD3QPxnrag=
    ServerName=PSNT
    [Database Options]
    ;=========================================================================
    ; Database-specific configuration options
    ;=========================================================================
    ; Please see Chapter "Tuning and Administration", in
    ; Sybase Installation and Administration Guide for details
    SybasePacketSize=512
    ; Please see Chapter "Tuning and Administration", in
    ; Oracle Installation and Administration Guide for details
    UseLocalOracleDB=0
    ;ORACLE_SID=
    OracleDisableFirstRowsHint=0
    ; Dynamic change allowed for EnableDBMonitoring (PSAESRV Only)
    EnableDBMonitoring=1
    [Trace]
    ;=========================================================================
    ; Trace settings
    ;=========================================================================
    ; PeopleTools trace file (NT only, ignored on UNIX)
    TraceFile=%PS_SERVDIR%\logs\PeopleTools.trc
    ; SQL Tracing Bitfield
    ; Bit Type of tracing
    ; 1 - SQL statements
    ; 2 - SQL statement variables
    ; 4 - SQL connect, disconnect, commit and rollback
    ; 8 - Row Fetch (indicates that it occurred, not data)
    ; 16 - All other API calls except ssb
    ; 32 - Set Select Buffers (identifies the attributes of columns
    ; to be selected).
    ; 64 - Database API specific calls
    ; 128 - COBOL statement timings
    ; 256 - Sybase Bind information
    ; 512 - Sybase Fetch information
    ; 1024 - SQL Informational Trace
    ; Dynamic change allowed for TraceSql and TraceSqlMask
    TraceSQL=0
    ; PeopleCode Tracing Bitfield
    ; Bit Type of tracing
    ; 1 - Trace Evaluator instructions (not recommended)
    ; 2 - List Evaluator program (not recommended)
    ; 4 - Show assignments to variables
    ; 8 - Show fetched values
    ; 16 - Show stack
    ; 64 - Trace start of programs
    ; 128 - Trace external function calls
    ; 256 - Trace internal function calls
    ; 512 - Show parameter values
    ; 1024 - Show function return value
    ; 2048 - Trace each statement in program (recommended)
    ; Dynamic change allowed for TracePC
    TracePC=0
    ; AE Tracing Bitfield
    ; Bit Type of tracing
    ; 1 - Trace STEP execution sequence to AET file
    ; 2 - Trace Application SQL statements to AET file
    ; 4 - Trace Dedicated Temp Table Allocation to AET file
    ; 8 - not yet allocated
    ; 16 - not yet allocated
    ; 32 - not yet allocated
    ; 64 - not yet allocated
    ; 128 - Timings Report to AET file
    ; 256 - Method/BuiltIn detail instead of summary in AET Timings Report
    ; 512 - not yet allocated
    ; 1024 - Timings Report to tables
    ; 2048 - DB optimizer trace to file
    ; 4096 - DB optimizer trace to tables
    TraceAE=0
    ; Performance Monitor Tracing Bitfield
    ; Bit Type of tracing
    ; 1 - Trace All performance monitor agent activity
    TracePPM=0
    [Process Scheduler]
    ;=========================================================================
    ; General settings for the Process Scheduler
    ;=========================================================================
    PrcsServerName=PSNT
    DBBIN=c:\Program Files\Microsoft SQL Server\80\Tools\Binn
    ; Max number of attempt to try reconnect to the database when the connection
    ; is lost
    Max Reconnect Attempt=12
    ; Interval in seconds between attempts to reconnect
    Reconnection Interval=300
    ; This parameter indicates the duration in minutes allotted before
    ; Tools' security module will timeout authenticating a process released
    ; by Process Scheduler. The timer starts from the time Process Scheduler
    ; initiates the request
    Authentication Timeout=5
    ; This allows for dynamic changes to certain setting without having to reboot
    ; the domain. The settings that can be dynamically changed are: Recycle Count,
    ; Consecutive Service failures, Trace SQL, Trace Mask SQL, TracePC,
    ; Log Fence, Enable DB Monitoring, and Enable Debugging.
    ; These settings are further identified by the "Dynamic change allowed for .."
    ; comment.
    Allow Dynamic Changes=N
    Log/Output Directory=C:\PT8.49\appserv\prcs\HC\log_output
    ; Log/Output Directory Extension Option
    ;An optional subdirectory structure that can be appended to the
    ;designated Log/Output Directory.
    ;Additional meta-string that can be used include
    ;Userid: %OPRID%
    ;Contentid: %REPORTID%
    ;Process Instance: %PRCSINSTANCE%
    ;Database Name: %DBNAME%
    ;Process Name: %PRCSNAME%
    ;Process Type: %PRCSTYPE%
    ;Scheduler Server Name: %SERVER%
    ;Current Date: %CURRDATE%
    ;Current Hour: %CURRHOUR%
    ;Job Name: %JOBNAME%
    ;Job Instance: %JOBINSTANCE%
    ; As an example for usage, %CURRDATE%\%CURRHOUR%
    Output Directory Optional Extension=
    ; Logging detail level
    ; Level Type of information
    ; -100 - Suppress logging
    ; 0 - Status information
    ; 1 - Critical Information
    ; 2 - Errors
    ; 3 - Informational (default)
    ; 4 - Tracing Level 1
    ; 5 - Tracing Level 2
    ; Dynamic change allowed for LogFence
    LogFence=3

  • Seperate NT service for App server and Process Scheduler

    Is it possible to create a separate NT service for App server and Process Schedule for the same environment? Everytime i need to shutdown either App Domain or Prcs Domain (not both) using service, it brings down both.
    I could use psadmin but services run as a different user.
    Please advise.

    What PeopleTools release are you using?  Off the top of my head, one strategy would be to use different PS_CFG_HOMEs for the App and the Process scheduler.  The service points to the PS_CFG_HOME and reads the pswinsrv.cfg file to know what to start/stop.  I'm not sure there is a way to override psntsrv and tell it to use a different config file, so you may need a different HOME.  You could also create a script that wraps the service start/stop.  It could edit/update the config file prior to stop/start and remove Process Scheduler from the config and then reinsert it later.
    You could have a stop_app/start_app and stop_prcs/start_prcs script that would copy in specific versions of the pswinsrv.cfg file for what you want to do.

  • PRCS SQR gives different format for (1) directly to printer (2) Web PDF

    I am running an SQR via process scheduler producing a report.
    The format and size are FINE when i run it directly to the printer. Command is below:
    %TOOLBINSRV%\PSSQR.EXE -CT ORACLE -CS %SERVER% -CD PS89C -CA %ACCESSID% -CAP %ACCESSPSWD% -RP NFCNT002 -I 161118 -R REFRESH -CO PSKT -OT 2 -OP \\nfbprint\SDT-INF-3 -OF 4 -LG ENG
    However, when I run and have it sent on the WEB with format PDF, the format is different
    The format is the same as above but about 40% smaller size.
    Different for when i open and see, and for when I print
    Anyone knows if there is an extra setup of step that i could add either on when running SQR on prcs, or on opening the file with Adobe acrobat ?
    Thanks

    Which one looks better, the web or printed?
    Seems like we had a similar problem a while back and the issue was with some scaling settings/preferences in the Acrobat Reader.

Maybe you are looking for