CRS not running in 1 node
Hi Experts,
CRS is not running in node 1 alone. Its running fine in node 2.
NODE 1 :
oracle@node1>crsctl check crs
Failure 1 contacting CSS daemon
Cannot communicate with CRS
Cannot communicate with EVM
NODE 2:
oracle@node2>crs_stat -t
Name Type Target State Host
ora....p1.inst application ONLINE OFFLINE
ora....p2.inst application ONLINE OFFLINE
ora.aixoppp.db application OFFLINE OFFLINE
ora....SM1.asm application ONLINE OFFLINE
ora....1T.lsnr application ONLINE OFFLINE
ora....01t.gsd application ONLINE OFFLINE
ora....01t.ons application ONLINE OFFLINE
ora....01t.vip application ONLINE ONLINE prop...p02t
ora....SM2.asm application ONLINE ONLINE prop...p02t
ora....2T.lsnr application ONLINE ONLINE prop...p02t
ora....02t.gsd application ONLINE ONLINE prop...p02t
ora....02t.ons application ONLINE ONLINE prop...p02t
ora....02t.vip application ONLINE ONLINE prop...p02t
AIX 5.3, 2 node RAC.
Please help me on this ?
Mission Critical
-Riaz Ahamed
Edited by: 805646 on Nov 5, 2010 4:24 AM
Hi,
Have you tried this command on node1 ?
crsctl start crs
Regards,
Levi Pereira
Similar Messages
-
Multiple VI instance will not RUN using invoke node
Hi,
I need to have multiple instances of the same VI running.
I've created a template of the VI i wan't to call multiple times.
The VI is called via Open VI reference with a reference to the VI template.
Parameters to the instance is passed via set control value.
When opened and parameters has been passed, I use a invoke node to run the VI.
An error occur.
"Error 1000 occurred at Invoke Node in Template_Call plot window.vi
Possible reason(s):
LabVIEW: The VI is not in a state compatible with this operation.
Method Name: Run VI
VI Path: NULL"
Note ! The VIs should stay open after the call running independently of each other and the caller should not be waiting until the VI stops.
Any ideas what I am doing wrong
Regards Kahr
Certified LabVIEW Architect
CIM A/S
Solved!
Go to Solution.
Attachments:
Call_Plot Window.png 31 KB
Template_Plot window.png 23 KBAs simple as that Kumar !
Thank You all
Regards Kahr
Certified LabVIEW Architect
CIM A/S -
QMASTER hints 4 usual trouble (QM NOT running/CLUSTEREd nodes/Networks etc
All, I just posted this with some hints & workaround with very common issues people have on this forum and keep asking concerning the use of APPLE QMASTER with FCP, SHAKE, COMPRESSOR and MOTION. I've had many over the last 2 years and see them coming up frequently.
Perhaps these symptoms are fixed in FCS2 at MAY 2007 (now). However if not here's some ROTS that i used for FCP to compressor via QMASTER cluster for example. NO special order but might help someone get around the stuff with QMASTER V2.3, FCP V5.1.4, compressor.app V2.3
I saw the latest QMASTER UI and usage at NAB2007 and it looked a little more solid with some "EASY SETUP" stuff. I hope it has been reworked underneath.. I guess I will know soon if it has.
For most FCP/COMPRESSOR, SHAKE. MOTION and COMPRESSOR:
• provide access from ALL nodes to ALL the source and target objects (files) on their VOLUMES. Simply MOUNT those volumes through the APPLE file system (via NFS) using +k (cmd+k) or finder/go/connect to server. OR using an SSAFS such as XSAN™ where the file systems are all shared over FC not the network. YOu will notice the CPU's going very busy for a small while. THhis is the APPLE FILE SYSTEM task,,, I guess it's doing 'spotlight stuff". This goes away after a few minutes.
• set the COMPRESSOR preferences for "CLUSTER OPTIONS" to "Never copy source to Cluster". This means that all nodes can access your source and target objects (files) over NFS (as above). Failure to to this means LENGTHY times to COPY material back an forth, in some cases undermining the pleasure gained from initially using clustering (reduced job times)
• DONT mix the PHYSICAL or LOGICAL networks in your local cluster. I dont know why but I could never get this to work. Physical mean stick with eother ETHERNET or FIREWIRE or your other (airport etc whic will be generally way to slow and useless), Logical measn leepin all nodes on the SAME subnet. You can do this siply by setting theis up in the system preferences/QMASTER/advanced tab under "Use Network Interfaces". In my currnet QUAd I set this to use BUILT IN ETHERNET1 and in the MPBDC's I set this to their BUILTIN ETHERNET.
• LOGICAL NETWORKS (Subnet): simply HARDCODE an IP address on the ETHERNET (for eample) for your cluster nodes andthe service controller. FOr eample 3.1.1.x .... it will all connect fine.
• Physical Networks: As above (1) DONT MIX firewire (IPoFW) and Ethernet(IPoE). (2) if more than extra service node USE A HUB or SWITCH. I went and bought a 10 port GbE HUB for about $HK400 (€40) and it worked fine. I was NEVER able to get a stable system of QMASTER mixing FW and ETHERNET. (3) fwiw using IP of FW caused me a LOAD of DISK errors and timouts (I/O errors) on thosse DISKs that were FW400 (al gone now) but it showed this was not stable overall
• for the cluster controller node MAKE SURE you set the CLUSTER STORAGE (system preferences/QMASTER/shared cluster storage) for the CLUSTER CONTROLLER NODE IS ON A SHARED volume (See above). This seems essential for SHAKE to work. (if not check the Qmaster errors in the console.app [see below] ). IF you have an SSAFS like XSAN™ then just add this cluster storage on a share file path. NOte that QMASTER does not permit the cluster storage to be on a NETWORK NODE for some reason. So in short just MOUNT the volume where the SHARED CLUSTER file is maintained for the CLUSTER controller.
• FCP - avoid EXPORT to COMPRESSOR from the TIMELINE - it never seems to work properly (see later). Instead EXPORT FROM SEQUENCE in the BROWSER - consistent results
• FCP - "media missing " messages on EXPORT to COMPRESSOR.. seems a defect in FCP 5.1 when you EXPORT using a sequence that is NOT in the "root" or primary trry in the FCP PROJECT BROWSER. Simply if you have browser/bin A contains(Bin B (contains Bin C (contains sequence X))) this will FAIL (wont work) for "EXPORT TO COMPRESSOR" if you use EXPORT to COMPRESSOR in a FCP browser PANE that is separately OPEN. To get around this, simply OPEN/EXPOSE the triangles/trees in the BROWSER PANE for the PROJECT and select the SEQUENCE you want and "EXPORT to COMPRESSOR" from there. This has been documented in a few places in this forum I think.
• FCP -> COMPRESSOR -> .M2V (for DVDSP3): some things here. EXPORTING from an FCP SEQUENCE with CHAPTER MARKERS to an MPEG2 .M2V encoding USING A CLUSTER causes errors in the placement of the chapter makers when it is imported to DVDSP3. In fact CONSISTENTLY, ALL the chapter markers are all PLACED AT THE END of the TRACK in DVD SP# - somewhat useless. This seems to happen ALSO when the source is an FCP reference movie, although inconsistent. A simple work around if you have the machines is TRUN OF SEGMENTING in the COMPRESSOR ENCODER inspector. let each .M2V transcode run on the same service node. FOr the jobs at hand just set up a CLUSTER and controller for each machine and then SELECT the cluster (myclusterA, hisclusterb, herclusterc) for each transcode job.. anyway for me.. the time spent resolving all this I could have TRANSCODED all this on my QUAD and it would all have ben done by sooner! (LOL)
• CONSOLE logs: IF QMASTER fails, I would suggest your fist port of diagnosis should be /Library/Logs/Qmaster in there you will see (on the controller node) compressor.log, jobcontroller.com.apple.qmaster.cluster.admin.log, and lots of others including service controller.com.apple.qmaster.executorX.log (for each cpu/core and node) andd qmasterca.log. All these are worth a look and for me helped me solve 90% of my qmaster errors and failures.
• MOTION 3 - fwiw.. EXPORT USING COMPRESSOR to a CLUSTER seems to fail EVERY TIME.. seems MOTION is writing stuff out to a /var/spool/qmaster
TROUBLESHOOTING QMASTER: IF QMASTER seems buggered up (hosed), then follow these steps PRIOR to restarting you machines.
go read the TROUBLE SHOOTING in the published APPLE docs for COMPRESSOR, SHAKE and "SET UP FOR DISTRIBUTED PROCESSING" and serach these forums CAREFULLY.. the answer is usually there somewhere.
ELSE THEN,, try these steps....
You'll feel that QMASTER is in trouble when you
• see that the QMASTER ICON at the top of the screen says 'NO SERVICES" even though that node is started and
• that the APPLE QMASTER ADMINSTRATOR is VERY SLOW after an 'APPLY" (like minutes with SPINNING BEACHBALL) or it WONT LET YOU DELETE a cluster or you see 'undefined' nodes in your cluster (meaning that one was shut down or had a network failure)..... all this means it's going to get worse and worse. SO DONT submit any more work to QAMSTER... best count you gains and follow this list next.
(a) in COMPRESSOR.app / RESET BACKGROUND PROCESSES (its under the COMPRESSOR name list box) see if things get kick started but you will lose all the work that has been done up to that point for COMPRESSOR.app
b) if no OK, then on EACH node in that cluster, STOP the QMASTER (system preferences/QMASTER/setup [set 0 minutes in the prompt and OK). Then when STOPPED, RESET the shared services my licking OPTION+CLICK on the "START" button to reveal the "RESET SERVICES". Then click "START" on each node to start the services. This has the actin of REMOVING or in the case where the CLUSTER CONTROLLER node is "RESET" f terminating the cluster that's under its control. IF so Simply go to APPLE QMASTER ADMINISTRATOR and REDFINE it. Go restart you cluster.
c) if step (b) is no help, consult the QMASTER logs in /Library/Logs/Qmaster (using the cosole.app) for any FILE MISSING or FILE not found or FILE ERROR . Look carefully for the NODENAME (the machine_name.local) where the error may have occured. Sometimes it's very chatty. Others it is not. ALso look in the BATCH MONITOR OUTPUT for errors messages. Often these are NEVER written (or I cant find them) in the /var/logs... try and resolve any issues you can see (mostly VOLUME or FILE path issues from my experience)
(d) if still no joy then - try removing all the 'dead' cluster files from /var/tmp/qmaster , /var/sppol/qmaster and also the file directory that you specified above for the controller to share the clustering. FOR shake issues, go do the same (note also where the shake shared cluster file path is - it can be also specified in the RENDER FILEOUT nodes prompt).
e) if all this WONT help you, its time to get the BIG hammer out. Simply, STOP all nodes of not stopped. (if status/mode is "STOPPING" then it [QMASTER] is truly buggered). DISMOUNT the network volumes you had mounted. and RESTART ALL YOUR NODES. Tis has the affect of RESTARTING all the QMASTERD tasks. YEs sure you can go in and SUDO restart them but it is dodgy at best because they never seem to terminate cleanly (Kill -9 etc) or FORCE QUIT.... is what one ends up doing and then STILL having to restart.
f) after restart perform steps from (B) again and it will be usually (but not always) right after that
LAstly - here's some posts I have made that may help others for QMASTER 2.3 .. and not for the NEW QMASTER as at MAy 2007...
Topic "qmasterd not running" - how this happened and what we did to fix it. - http://discussions.apple.com/message.jspa?messageID=4168064#4168064
Topic: IP over Firewire AND Ethernet connected cluster? http://discussions.apple.com/message.jspa?messageID=4171772#4171772
LAstly spend some DEDICATED time to using OBJECTIVE keywords to search the FINAL CUT PRO, SHAKE, COMPRESSOR , MOTION and QMASTER forums
hope thats helps.
G5 QUAD 8GB ram w/3.5TB + 2 x 15in MBPCore Mac OS X (10.4.9) FCS1, SHAKE 4.1Warwick,
Thanks for joining the forum and for doing all this work and posting your results for our benefit.
As FCP2 arrives in our shop, we will try once again to make sense of it and to see if we can boost our efficiencies in rendering big projects and getting Compressor to embrace five or six idle Macs.
Nonetheless, I am still in "Major Disbelief Mode" that Apple has done so little to make this software actually useful.
bogiesan -
Dbms_schduler job is not running on a 2 node rac when 1st node fails
Hi,
I want to create a dbms_scheduler job in a 2 node RAC and the job should always run on the node1 and if node1 is down then it should run on node2. This is Oracle 10gR2 (10.2.0.3 in WINDOWS) .In order to do the same I did following
-- First Step
Using DBCA- Service Managment - Created a service (BATCH_SERVICE) and given node1 as preferred and node2 as available. This created following entry in tnsnames.ora in both nodes.
BATCH_SERVICE =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = node1-vip)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = node2-vip)(PORT = 1521))
(LOAD_BALANCE = yes)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = BATCH_SERVICE)
(FAILOVER_MODE =
(TYPE = SELECT)
(METHOD = BASIC)
(RETRIES = 180)
(DELAY = 5)
--- Step 2
-- Created BATCH job classes.
BEGIN
DBMS_SCHEDULER.create_job_class(
job_class_name => 'BATCH_JOB_CLASS',
service => 'BATCH_SERVICE');
END;
-- Step 3 -- created a job using job_class as BATCH_JOB_CLASS
begin
dbms_scheduler.create_job(
job_name => 'oltp_job_test'
,job_type => 'STORED_PROCEDURE'
,job_action => 'schema1.P1'
,start_date => systimestamp at time zone 'US/Central'
,repeat_interval => 'FREQ=DAILY;BYHOUR=11;BYMINUTE=30;'
,job_class => 'BATCH_JOB_CLASS'
,enabled => TRUE
,comments => 'New Job.');
end;
Now when I monitor this job it runs on node1. Now I started testing for failover. I manually shutdown 1st instance. Then as per my understanding job should run on 2nd node. But job is not picking up.
when I run the followign command
srvctl status service -d db -s BATCH_SERVICE
service BATCH_SERVICE is running on instance node2.
Any help is really appreciated.It does not show that whether job is running or broken.
-
Azure Compute Nodes not running the job
I have an on-premise head node. I have joined 10 Azure Compute Nodes via the cloud service and storage account. I have uploaded the dlls directory to storage account and synced using hpcsync all the compute nodes. The Azure compute nodes are still not
running the job. I see in the HPC Job Manager that the Cores In Use = 0. How should I resolve this issue?Hello,
We are researching on the query and would get back to you soon on this.
I apologize for the inconvenience and appreciate your time and patience in this matter.
Regards,
Azam khan -
Hi,
We had installed RAC DB namely ORCL on a two-node cluster abcoracledb01 and abcoracledb02 with the OUI launched from db01 node. After installation, the NETCA is able to identify the RAC DB ORCL on both the nodes as well as the ORCL1 instance on db01 node and ORCL2 instance on db02 node. Now when I try to launch the DBCA from db01 node, it prompts me with the two normal options Real Applications Cluster database and normal database on its welcome screen as it detects the CRS running on this node. The problem is coming when Im trying to launch DBCA from the second node as it does not extends the RAC option in its welcome screen. I can understand that the CRS is not running on this db02 instance and and i verified this by running the OLSNODES -v command that gives me an error stating that the cluster interface is not getting started.
Will highly appreciate if anyone can help me to get some referenctial documentation or diagnostic information that may help me in troubsleshooting the exact reason behind the CRS not getting started.
Thanks,
Manoj ([email protected])Ummm... Why are you trying to run the DBCA twice? The DBCA is really only there to give you a starter database configured for either OLTP, OLAP, or multi-purpose, but since both nodes will be attached to the same database, you shouldn't run the DBCA more than once. Once you have the database created with DBCA, attach the second node to it and go. Your problem is not with DBCA, it's in the cluster interconnect. Once that starts up, the second instance will attach to the database and go.
-
How does RAC determine which instance number to run on which node
Good afternoon
I am trying to script a process and I need to identify how RAC decides which node runs which instance. Is it the first one of the pair added to the cluster that runs node 1 or is there some other piece of information that I need to work this out
This is on Redhat Linux with 10.2.0.3 for CRS, ASM and databases
Cheers
PeterBefore "you" start an instance you set env variable ORACLE_SID. This identifies an instance. When you go into sqlplus and issue STARTUP, Oracle starts the instance named by the sid. Thus the instance running on the server is controlled by you. This changes as noted below.
If you were using a non-Oracle tool to start instances, such as Veritas, then you would see it start the instance you coded into the tool. It would not randomly pick an instance. It looks in the Veritas config file and sees that you always want instance 1 on this node and instance 2 on that node.
That said, you can make Oracle more random or "grid" like. 10g RAC done Oracle's way likes to bounce around between primary and secondary nodes. To see which instances are running on a node you can "ps -ef | grep pmon". Alternatively, use sqlplus to look in the database: view gv$instance gives you each instance name paired with the name of the host it is currently running on. There is one line of output per instance currently running.
-Mark -
CRS not starting after Oracle 11g Grid was succesuflly installed
Hi:
Have 2 node RAC. My Shared storage is on openfiler.
Oracle 11g Grid was successfully installed and all the services was working fine. When i restarted the system I found CRS was not coming up. Remaining processes were up and running.
Let me explain what I did: (O/s RHEL 5.4 & oracle 11g R2 grid)
I have a partition in shared disk /dev/sdc1 (I have other partitions, but thought of using only one for OCR and voting disk). (did not define it as raw partition as I used to do in 10g RAC).
While installing Oracle grid and when it prompted to enter the Diskgroup for OCR and Voting disk I gave a name DGDATA and choose only one (external redundancy) disk “/dev/sdc1″ (it does not ask for one for OCR and one for Voting as it used to do in 10g clusterware installation). As per my assumption both OCR and Voting disk were created within /dev/sdc1 (after installation when I queried I got the same info)
The Oracle grid installation has gone through successfully. when I restart the system I find CRS not starting.
The log says: “Error PROC:26: Error while accessing the physical storage ASM……..
ORA-01034: oracle not available...
Could not init OCR, code:26….
Linux permission denied".
For your information….ASM instance is up (check in both the nodes) and I find the diskgroup mounted.
Can anyone help on this.
Also let me know how to uninstall Oracle 11g Grid software and configuration. If I have to reinstall the Oracle 11g grid software and config once again is it possible without reinstalling RHEL. Let me know the steps or any link please. don't want to get into a mess again.
Thanks in advance.
Regards
DineshJorg, I even tried to nomount the DB instance using initDBRAC.ora pfile. Then tried to create spfile still got the same error.
The second trace file which I have pasted looks like some memory dump.
ASM_DISKSTRING= /dev/sdc*
***********************************************************************1st trace file
Fatal NI connect error 12547, connecting to:
(DESCRIPTION=(ADDRESS=(PROTOCOL=beq)(PROGRAM=/crs/11.2.0/grid/bin/oracle)(ARGV0=oracle+ASM1_o000_dbrac)(ENVS='ORACLE_HOME=/crs/11.2.0/grid,ORACLE_SID=+ASM1')(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))'))(enable=setuser)(CONNECT_DATA=(CID=(PROGRAM=oracle@skyit6)(HOST=skyit6)(USER=oracle))))
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.1.0 - Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
Time: 01-JUN-2011 01:27:07
Tracing not turned on.
Tns error struct:
ns main err code: 12547
TNS for Linux: Version 11.2.0.1.0 - Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
Time: 01-JUN-2011 01:27:07
Tracing not turned on.
Tns error struct:
ns main err code: 12547
TNS-12547: TNS:lost contact
ns secondary err code: 12560
nt main err code: 517
TNS-00517: Lost contact
nt secondary err code: 32
nt OS err code: 0
ERROR: Failed to connect with connect string: (DESCRIPTION=(ADDRESS=(PROTOCOL=beq)(PROGRAM=/crs/11.2.0/grid/bin/oracle)(ARGV0=oracle+ASM1_o000_dbrac)(ENVS='ORACLE_HOME=/crs/11.2.0/grid,ORACLE_SID=+ASM1')(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))'))(enable=setuser))
Wed Jun 01 01:27:07 2011
ERROR: slave communication error with ASM; terminating process 16772
Errors in file /oraeng/app/oracle/product/diag/rdbms/dbrac/DBRAC/trace/DBRAC_ora_16772.trc:
----======================2nd trace file
Trace file /oraeng/app/oracle/product/diag/rdbms/dbrac/DBRAC/trace/DBRAC_ora_16772.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Real Application Clusters option
ORACLE_HOME = /oraeng/app/oracle/product/11.2.0
System name: Linux
Node name: skyit6
Release: 2.6.18-164.el5
Version: #1 SMP Tue Aug 18 15:51:54 EDT 2009
Machine: i686
Instance name: DBRAC
Redo thread mounted by this instance: 0 <none>
Oracle process number: 25
Unix process pid: 16772, image: oracle@skyit6 (TNS V1-V3)
*** 2011-06-01 01:27:07.010
*** SESSION ID:(1.3) 2011-06-01 01:27:07.010
*** CLIENT ID:() 2011-06-01 01:27:07.010
*** SERVICE NAME:() 2011-06-01 01:27:07.010
*** MODULE NAME:(sqlplus@skyit6 (TNS V1-V3)) 2011-06-01 01:27:07.010
*** ACTION NAME:() 2011-06-01 01:27:07.010
ERROR: slave communication error with ASM; terminating process 16772
*** 2011-06-01 01:27:07.035
dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x0, level=2, mask=0x0)
----- Error Stack Dump -----
----- Current SQL Statement for this session (sql_id=bff5sku8phfgx) -----
create spfile='+dgasmspfile/spfileDBRAC.ora' from pfile
*** 2011-06-01 01:27:07.070
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
skdstdst()+41 call kgdsdst() BF9E05FC ? 2 ?
ksedst1()+77 call skdstdst() BF9E05FC ? 0 ? 1 ? AB80E70 ?
852F42A ? AB80E70 ?
ksedst()+33 call ksedst1() 0 ? 1 ?
dbkedDefDump()+2699 call ksedst() 0 ? 0 ? BF9E0D40 ? 0 ? 0 ?
0 ?
ksedmp()+47 call dbkedDefDump() 2 ? 0 ?
kfTerminateMe()+75 call ksedmp() 2 ? 3 ? F1170AC ? F149234 ?
5 ? BF9E0A6C ?
kfnCheckCommError() call kfTerminateMe() F149234 ? BF9E0C1C ?
+32 B033D83 ? 29392378 ?
F149234 ? EB00601 ?
kfncSlaveSubmit()+5 call kfnCheckCommError() 29392378 ? F149234 ?
83
kfncFileDelete()+11 call kfncSlaveSubmit() BF9E0E5C ? 0 ? F147B24 ?
81
kfioDelete()+126 call kfncFileDelete() 29DEE0 ? 1C ?
ksfddel1()+582 call kfioDelete() 29DEE0 ? 1C ? D ?
ksfddel()+187 call ksfddel1() 29DEE0 ? 1C ? D ? 0 ?
BF9E0F2C ? 9BA2 ?
ksp_spfile_create() call ksfddel() 29DEE0 ? 1C ? D ? 0 ?
+677
kspcspfp()+791 call ksp_spfile_create() BF9E49D4 ? 0 ? 29DEE0 ? 1C ?
7D02 ? 0 ?
kspocte()+67 call kspcspfp() 29DEE0 ? 1C ? F074CC4 ? F ?
61,1 1%
Regards
Dinesh -
Orainst.sh scripts not respond on RAC Node 2
Hi every one,
I am configuring RAC with 2 nodes. during cluster installation the root.sh and orainst.sh runs successfully on Node1.. root.sh scripts also runs fine on Node 2...but when running orainst.sh scripts its starts and hangs on "90 seconds" nothing happens ...
Any one have idea..
Thanks..
AzizAbdul Aziz wrote:
Hi Billy, sorry for not mentioning... I have Linux rhel 4.6 and Oracle 10g Clusterware 10.2.....
We have installed many time before but on rhel 4.3..
Had a similar problem due to bug 4679769. As I recall, the configuration/checking of the OCR (and/or Voting) Disks fails when checked by the installer script on subsequent nodes after the 1st node formatted it.
I hacked it originally by removing certain checks from the shell script (not recommended). Later when installing other clusters discovered that module clsfmt.bin was the problem and that patch 4679769 provides a replacement module. The patch is not opatch style - simply a manual copy to replace the existing module with the updated one.
But this was for Linux x86-64 (AMD64/EM64T). You neglected to name the h/w platform. But I suspect the same problem would exist for Intel based platforms.
An alternative (which I am using with current CRS installs) is to install CRS 11g and run 10gr2 RAC on top of it. It is a certified combo and hopefully will result in less work when I need to upgrade the RDBMS to 11.2 when it becomes available. -
SAPOSCOL not running in MS Cluster
Hi, gurus:
We have a problem with SAPOSCOL in a SAP ECC 6.0 system (SAP ECC 6.0 + NetWeaver 7.00 + Oracle 10.2 + Windows Server 2003 R2 Enterprise x64 Edition) running over a MS cluster:
Transactions OS06/ST06 shows no data, and they show an info message wich states: SAPOSCOL not running ? (shared memory not available ). When we checked this issue, we noticed that, in fact, there is no sapcoscol.exe task running in any node.
But when we try to start the service (both using microsoft services console and cmd commands) although we can see the process running in the node which owns all the resources, SAP seems not notice that. The information system shows in ST06>Operating System Collector>Status is the following:
iinterval 0 sec.
Collector Version:
Date/time 05.09.2008 16:55:01
Start of Collector
Status report
Collector Versions
running COLL 20.95 700 - 20.64 NT 07/10/17
dialog COLL 20.95 700 - 20.65 NT 08/02/06
Shared Memory attached
Number of records 575
Active Flag active (01)
Operating System Windows NT 5.2.3790 SP 2 BL-SAP2 4x AMD64 Level 1
Collector PID 0 (00000000)
Collector not running (process ID not found).
Start time coll. Thu Jan 01 01:00:00 1970
Current Time Fri Sep 05 16:55:01 2008
Last write access Mon Sep 01 11:28:23 2008
Last Read Access Fri Sep 05 15:54:00 2008
Collection Interval 10 sec (next delay).
Collection Interval 10 sec (last ).
Status read
Collect Details required
Refresh required
Header Extention Structure
Number of x-header Records 1
Number of Communication Records 60
Number of free Com. Records 60
Resulting offset to 1.data rec. 61
Trace level 3
Collector in IDLE - mode ? NO
become idle after 300 sec without read access.|
Length of Idle Interval 60 sec
Length of norm.Interval 10 sec
But saposcol.exe is running with a certain PID in the same note than SAP and Oracle under user sapservice<sid>
We have tried to run saposcol in several ways (as, I have noted before: from microsoft service console, from cmd line using "net start saposcol", using the saposcol under C:\WINDOWS\SapCluster and the one under
F:\usr\sap\PRD\sys\exe\run, fom the two nodes, accessing the cluster through several IPs...) and tried the commands saposcol -c and saposcol -k but we cannot get the saposcoll run. Moreover, we haven't found any log information. The only log we (and SAP) could find is the one located in C:\WINDOWS\SapCluster\dev_coll.
This log remain frozen at September 1st:
SAPOSCOL version COLL 20.95 700 - 20.64 NT 07/10/17, 64 bit, multithreaded, Non-Unicode
compiled at Feb 3 2008
systemid 562 (PC with Windows NT)
relno 7000
patch text COLL 20.95 700 - 20.64 NT 07/10/17
patchno 146
intno 20050900
running on BL-SAP2 Windows NT 5.2 3790 Service Pack 2 4x AMD64 Level 15 (Mod 65 Step 3)
12:04:16 01.09.2008 LOG: Profile : no profile used
12:04:16 01.09.2008 LOG: Saposcol Version : [COLL 20.95 700 - 20.64 NT 07/10/17]
12:04:16 01.09.2008 LOG: Working directory : C:\WINDOWS\SAPCLU~1
12:04:16 01.09.2008 LOG: Allocate Counter Buffer [10000 Bytes]
12:04:16 01.09.2008 LOG: Allocate Instance Buffer [10000 Bytes]
12:04:17 01.09.2008 LOG: Shared Memory Size: 71898.
12:04:17 01.09.2008 LOG: Connected to existing shared memory.
12:04:17 01.09.2008 LOG: MaxRecords = 575 <> RecordCnt + Dta_offset = 614 + 61
12:04:22 01.09.2008 WARNING: WaitFree: could not set new shared memory status after 5 sec
12:04:22 01.09.2008 WARNING: Cannot create Shared Memory
Kernel Info:
Kernel release 700
Compilation NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00
Sup.Pkg lvl. 146
ABAP Load 1563
CUA load 30
Mode opt
Can anyone shed some light on the subject?
Thank you very much and kind regards
Edited by: Jose Enrique Sepulveda on Sep 6, 2008 2:10 AMDear bhaskar:
Thanks for your reply. We have considered balancing the system to the other node or reboot the system to free resources, in order to re-create the shared memory, but in the past, the balancing process (move resources from one node to the other) has caused problems. Since this is a critical system, stopping (or balancing) is not an option right now, and updating the kernel requires an ABAP stack reboot plus the kernel change : any changes in system configuration requires a longer approval/planning process than a reboot.
Moreover, the OS collecting system and its display in OS06/ST06 has worked fine until now.
Does anyone knows if a reboot has solved this kind of problem in a similar situation?
Thanks in advance
José Enrique -
CCMS alert not running automatically
Hi,
Can take little time and read this one and please let me know where i am getting mistake, and is anyone can fix alert please let me know
Thanks in Advanced
1. SAPKB64020 Basis Support Package 20 for 6.40 imported at 13.12.2007
2. check SU01 User Roles SAP_BC_BASIS_ADMIN, SAP_BC_ALM_CUST, SAP_ALM_ADMINISTRATOR, SAP_BC_ALM_ALERT_USER
3. check SU01 comm.meth: e m a i l
4. User Profile: S_A.SCON, SAP_ALL
5. SMTP configured fine, internal mail works fine
6. RZ21 - Copied CCMS_OnAlert_E m a i l to ZCCMS_OnAlert_E m a i l
Execution Tab: Function Modle (SALO_M A I L_IN_CASE_OF_ALERT)
Execute method on group (any server)
Control Tab: Execute method (Periodically in dialog process
Startup method group (checked -Execute method immediately after monitoring segment start- )
Selected (On all application servers)
Paramaters Tabe: SENDER: awan_t
RECIPIENT:user @ company . com
RECIPIENT-TYPEID: U
SUBJECT_ALERT: This is CCMS from $SID
$NODENAME
$SEGMENT: Segment name node (= $INSTANCE )
Release Tabe: (Checked Auto-reaction)
7. RZ20 - SAP CCMS Monitor Templates
--> Entire System
--> XDV
--> Appication Server
--> SID ID
--> Operating System
--> Memory
--> Free Memory
Selected Free memory and click properity
Performance Attribute Tab: Comparison value (Selected Last reported value)
Green to Yellow 10MB
Yellow to Red 20MB
Red to Yellow 10MB
Rest from yellow to green 5mb
Method Tab: Data collection method: CCMS_Mem_Collect_c
auto-reaction method: zCCMS_OnAlert_mail
Analysis method: CCMS_OS_Analze
8. Goback to MTE Free memory (Refresh) and click open alert pushbutton
it shows Free memory [ 1 Alert ], 49BM < 20 MB current value below throshold value
9. click Extras from menu and actived mantannce function
10. Goto EDIT from menu --> Nodes (MTE) --> Start method --> Start auto-reaction method
11. I received e-mail when I started auto-reaction method
Alert not running automacally ?Hi,
Can take little time and read this one and please let me know where i am getting mistake, and is anyone can fix alert please let me know
Thanks in Advanced
1. SAPKB64020 Basis Support Package 20 for 6.40 imported at 13.12.2007
2. check SU01 User Roles SAP_BC_BASIS_ADMIN, SAP_BC_ALM_CUST, SAP_ALM_ADMINISTRATOR, SAP_BC_ALM_ALERT_USER
3. check SU01 comm.meth: e m a i l
4. User Profile: S_A.SCON, SAP_ALL
5. SMTP configured fine, internal mail works fine
6. RZ21 - Copied CCMS_OnAlert_E m a i l to ZCCMS_OnAlert_E m a i l
Execution Tab: Function Modle (SALO_M A I L_IN_CASE_OF_ALERT)
Execute method on group (any server)
Control Tab: Execute method (Periodically in dialog process
Startup method group (checked -Execute method immediately after monitoring segment start- )
Selected (On all application servers)
Paramaters Tabe: SENDER: awan_t
RECIPIENT:user @ company . com
RECIPIENT-TYPEID: U
SUBJECT_ALERT: This is CCMS from $SID
$NODENAME
$SEGMENT: Segment name node (= $INSTANCE )
Release Tabe: (Checked Auto-reaction)
7. RZ20 - SAP CCMS Monitor Templates
--> Entire System
--> XDV
--> Appication Server
--> SID ID
--> Operating System
--> Memory
--> Free Memory
Selected Free memory and click properity
Performance Attribute Tab: Comparison value (Selected Last reported value)
Green to Yellow 10MB
Yellow to Red 20MB
Red to Yellow 10MB
Rest from yellow to green 5mb
Method Tab: Data collection method: CCMS_Mem_Collect_c
auto-reaction method: zCCMS_OnAlert_mail
Analysis method: CCMS_OS_Analze
8. Goback to MTE Free memory (Refresh) and click open alert pushbutton
it shows Free memory [ 1 Alert ], 49BM < 20 MB current value below throshold value
9. click Extras from menu and actived mantannce function
10. Goto EDIT from menu --> Nodes (MTE) --> Start method --> Start auto-reaction method
11. I received e-mail when I started auto-reaction method
Alert not running automacally ? -
Server Process is not running in the WAS JAVA
Hi,
The WAS JAVA have the resources Netweaver7.0 and java is j2sdk1.4.2_13 version Operating system is Windows2003 and database server is SQLserver2005.
Previously it was running properly Now it giving the following Error.
Any one of you please give me suggestions how to solve it .
Devolper trace for the jcontol.exe process is as follows
trc file: "D:\usr\sap\NW2\JC02\work\dev_jcontrol", trc level: 1, release: "700"
node name : jcontrol
pid : 4516
system name : NW2
system nr. : 02
started at : Mon Mar 24 17:07:20 2008
arguments :
arg[00] : D:\usr\sap\NW2\JC02\exe\jcontrol.EXE
arg[01] : pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] *** WARNING => INFO: Unknown property [instance.box.number=NW2JC02mmsr17] [jstartxx.c 841]
[Thr 4512] *** WARNING => INFO: Unknown property [instance.en.host=mmsr17] [jstartxx.c 841]
[Thr 4512] *** WARNING => INFO: Unknown property [instance.en.port=3203] [jstartxx.c 841]
[Thr 4512] *** WARNING => INFO: Unknown property [instance.system.id=2] [jstartxx.c 841]
JStartupReadInstanceProperties: read instance properties [D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties;D:\usr\sap\NW2\JC02\SDM\program\config\sdm_jstartup.properties]
-> ms host : mmsr17
-> ms port : 3903
-> OS libs : D:\usr\sap\NW2\JC02\j2ee\os_libs
-> Admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Used property files
-> files [00] : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> files [01] : D:\usr\sap\NW2\JC02\SDM\program\config\sdm_jstartup.properties
Instance properties
-> ms host : mmsr17
-> ms port : 3903
-> os libs : D:\usr\sap\NW2\JC02\j2ee\os_libs
-> admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Bootstrap nodes
-> [00] bootstrap : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> [01] bootstrap_ID28653700 : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> [02] bootstrap_ID28653750 : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID28653700 : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> [01] ID28653750 : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> [02] sdm : D:\usr\sap\NW2\JC02\SDM\program\config\sdm_jstartup.properties
[Thr 4512] JControlExecuteBootstrap: execute bootstrap process [bootstrap]
[Thr 4512] [Node: bootstrap] java home is set by profile parameter
Java Home: C:\j2sdk1.4.2_13
[Thr 4512] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\NW2\JC02\exe\jvmx.jar
JStartupIReadSection: read node properties [bootstrap]
-> node name : bootstrap
-> node type : bootstrap
-> node execute : yes
-> java path : C:\j2sdk1.4.2_13
-> java parameters : -Djco.jarm=1
-> java vm version : 1.4.2_13-b06
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 256M
-> root path : D:\usr\sap\NW2\JC02\j2ee\cluster
-> class path : .\bootstrap\launcher.jar
-> OS libs path : D:\usr\sap\NW2\JC02\j2ee\os_libs
-> main class : com.sap.engine.offline.OfflineToolStart
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : D:\usr\sap\NW2\JC02\exe\jstartup.jar;D:\usr\sap\NW2\JC02\exe\jvmx.jar
-> parameters : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID0286537
-> debuggable : yes
-> debug mode : no
-> debug port : 60000
-> shutdown timeout : 120000
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_bootstrap
-> arg[03] = -nodeId=-1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=bootstrap
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_bootstrap.out
-> arg[08] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_bootstrap.out
-> arg[09] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_bootstrap
-> arg[10] = -mode=BOOTSTRAP
-> arg[11] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlExecuteBootstrap: read instance values after global bootstrap
[Thr 4512] *** WARNING => INFO: Unknown property [instance.box.number=NW2JC02mmsr17] [jstartxx.c 841]
[Thr 4512] *** WARNING => INFO: Unknown property [instance.en.host=mmsr17] [jstartxx.c 841]
[Thr 4512] *** WARNING => INFO: Unknown property [instance.en.port=3203] [jstartxx.c 841]
[Thr 4512] *** WARNING => INFO: Unknown property [instance.system.id=2] [jstartxx.c 841]
JStartupReadInstanceProperties: read instance properties [D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties;D:\usr\sap\NW2\JC02\SDM\program\config\sdm_jstartup.properties]
-> ms host : mmsr17
-> ms port : 3903
-> OS libs : D:\usr\sap\NW2\JC02\j2ee\os_libs
-> Admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
[Thr 4512] JControlExecuteBootstrap: enumerate the nodes after global bootstrap
Used property files
-> files [00] : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> files [01] : D:\usr\sap\NW2\JC02\SDM\program\config\sdm_jstartup.properties
Instance properties
-> ms host : mmsr17
-> ms port : 3903
-> os libs : D:\usr\sap\NW2\JC02\j2ee\os_libs
-> admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Bootstrap nodes
-> [00] bootstrap : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> [01] bootstrap_ID28653700 : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> [02] bootstrap_ID28653750 : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID28653700 : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> [01] ID28653750 : D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> [02] sdm : D:\usr\sap\NW2\JC02\SDM\program\config\sdm_jstartup.properties
[Thr 4512] JControlExecuteBootstrap: execute bootstrap process [bootstrap_ID28653700]
[Thr 4512] [Node: dispatcher bootstrap] java home is set by profile parameter
Java Home: C:\j2sdk1.4.2_13
[Thr 4512] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\NW2\JC02\exe\jvmx.jar
JStartupIReadSection: read node properties [bootstrap_ID28653700]
-> node name : dispatcher bootstrap
-> node type : bootstrap
-> node execute : yes
-> jlaunch parameters :
-> java path : C:\j2sdk1.4.2_13
-> java parameters : -Djco.jarm=1
-> java vm version : 1.4.2_13-b06
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 256M
-> root path : D:\usr\sap\NW2\JC02\j2ee\cluster
-> class path : .\bootstrap\launcher.jar
-> OS libs path : D:\usr\sap\NW2\JC02\j2ee\os_libs
-> main class : com.sap.engine.offline.OfflineToolStart
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : D:\usr\sap\NW2\JC02\exe\jstartup.jar;D:\usr\sap\NW2\JC02\exe\jvmx.jar
-> parameters : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID028653700
-> debuggable : yes
-> debug mode : no
-> debug port : 60000
-> shutdown timeout : 120000
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_bootstrap
-> arg[03] = -nodeId=-1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=bootstrap_ID28653700
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_bootstrap_ID28653700.out
-> arg[08] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_bootstrap_ID28653700.out
-> arg[09] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_bootstrap_ID28653700
-> arg[10] = -mode=BOOTSTRAP
-> arg[11] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlExecuteBootstrap: execute bootstrap process [bootstrap_ID28653750]
[Thr 4512] [Node: server0 bootstrap] java home is set by profile parameter
Java Home: C:\j2sdk1.4.2_13
[Thr 4512] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\NW2\JC02\exe\jvmx.jar
JStartupIReadSection: read node properties [bootstrap_ID28653750]
-> node name : server0 bootstrap
-> node type : bootstrap
-> node execute : yes
-> jlaunch parameters :
-> java path : C:\j2sdk1.4.2_13
-> java parameters : -Djco.jarm=1
-> java vm version : 1.4.2_13-b06
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 256M
-> root path : D:\usr\sap\NW2\JC02\j2ee\cluster
-> class path : .\bootstrap\launcher.jar
-> OS libs path : D:\usr\sap\NW2\JC02\j2ee\os_libs
-> main class : com.sap.engine.offline.OfflineToolStart
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : D:\usr\sap\NW2\JC02\exe\jstartup.jar;D:\usr\sap\NW2\JC02\exe\jvmx.jar
-> parameters : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID028653750
-> debuggable : yes
-> debug mode : no
-> debug port : 60000
-> shutdown timeout : 120000
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_bootstrap
-> arg[03] = -nodeId=-1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=bootstrap_ID28653750
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_bootstrap_ID28653750.out
-> arg[08] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_bootstrap_ID28653750.out
-> arg[09] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_bootstrap_ID28653750
-> arg[10] = -mode=BOOTSTRAP
-> arg[11] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlIBuildProcessList: Maximum error count is set to 4
[Thr 5144] JControlRequestFunc: Thread 5144 started as listener thread for np messages.
[Thr 4512] [Node: dispatcher] java home is set by profile parameter
Java Home: C:\j2sdk1.4.2_13
[Thr 4512] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\NW2\JC02\exe\jvmx.jar
JStartupIReadSection: read node properties [ID28653700]
-> node name : dispatcher
-> node type : dispatcher
-> node execute : yes
-> jlaunch parameters :
-> java path : C:\j2sdk1.4.2_13
-> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -XX:NewSize=57m -XX:MaxNewSize=57m -XX:NewRatio=3 -XX:DisableExplicitGC -verbose:gc -XX:UseConcMarkSweepGC
-> java vm version : 1.4.2_13-b06
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 170M
-> init heap size : 170M
-> root path : D:\usr\sap\NW2\JC02\j2ee\cluster\dispatcher
-> class path : .\bin\boot\boot.jar;.\bin\system\bytecode.jar;.
-> OS libs path : D:\usr\sap\NW2\JC02\j2ee\os_libs
-> main class : com.sap.engine.boot.Start
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : D:\usr\sap\NW2\JC02\exe\jstartup.jar;D:\usr\sap\NW2\JC02\exe\jvmx.jar
-> parameters :
-> debuggable : no
-> debug mode : no
-> debug port : 60000
-> shutdown timeout : 120000
[Thr 4512] [Node: server0] java home is set by profile parameter
Java Home: C:\j2sdk1.4.2_13
[Thr 4512] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\NW2\JC02\exe\jvmx.jar
JStartupIReadSection: read node properties [ID28653750]
-> node name : server0
-> node type : server
-> node execute : yes
-> jlaunch parameters :
-> java path : C:\j2sdk1.4.2_13
-> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -XX:MaxPermSize=256M -XX:PermSize=256M -XX:NewSize=171M -XX:MaxNewSize=171M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
-> java vm version : 1.4.2_13-b06
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 1024M
-> init heap size : 1024M
-> root path : D:\usr\sap\NW2\JC02\j2ee\cluster\server0
-> class path : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path : D:\usr\sap\NW2\JC02\j2ee\os_libs
-> main class : com.sap.engine.boot.Start
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : D:\usr\sap\NW2\JC02\exe\jstartup.jar;D:\usr\sap\NW2\JC02\exe\jvmx.jar
-> parameters :
-> debuggable : yes
-> debug mode : yes
-> debug port : 50221
-> shutdown timeout : 120000
[Thr 4512] INFO: Invalid property value [Debbugable=yes]
[Thr 4512] [Node: SDM] java home is set by profile parameter
Java Home: C:\j2sdk1.4.2_13
[Thr 4512] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\NW2\JC02\exe\jvmx.jar
JStartupIReadSection: read node properties [sdm]
-> node name : SDM
-> node type : sdm
-> node execute : yes
-> java path : C:\j2sdk1.4.2_13
-> java parameters :
-> java vm version : 1.4.2_13-b06
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 256M
-> root path : D:\usr\sap\NW2\JC02\SDM\program
-> class path : D:\usr\sap\NW2\JC02\SDM\program\bin\SDM.jar
-> OS libs path : D:\usr\sap\NW2\JC02\j2ee\os_libs
-> main class : SDMInternal
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : D:\usr\sap\NW2\JC02\exe\jstartup.jar;D:\usr\sap\NW2\JC02\exe\jvmx.jar
-> shutdown class : com.sap.sdm.jstartup.shutdown.InternalShutDown
-> parameters : server sdmhome=D:\usr\sap\NW2\JC02\SDM\program
-> debuggable : yes
-> debug mode : no
-> debug port : 60000
-> shutdown timeout : 120000
[Thr 4512] JControlMSConnect: attached to message server (mmsr17/3903)
[Thr 5340] JControlMSMessageFunc: Thread 5340 started as listener thread for ms messages.
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_dispatcher
-> arg[03] = -nodeId=0
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=ID28653700
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_dispatcher.out
-> arg[08] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_dispatcher.out
-> arg[09] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_dispatcher
-> arg[10] = -mode=JCONTROL
-> arg[11] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] JControlICheckProcessList: process dispatcher started (PID:5444)
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=ID28653750
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
-> arg[08] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
-> arg[09] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
-> arg[10] = -mode=JCONTROL
-> arg[11] = -debugMode=yes
-> arg[12] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] JControlICheckProcessList: process server0 started (PID:4684)
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_sdm
-> arg[03] = -nodeId=2
-> arg[04] = -file=D:\usr\sap\NW2\JC02\SDM\program\config\sdm_jstartup.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=sdm
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_sdm.out
-> arg[08] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_sdm.out
-> arg[09] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_sdm
-> arg[10] = -mode=JCONTROL
-> arg[11] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] JControlICheckProcessList: process SDM started (PID:5472)
[Thr 4512] JControlMSSendLogon: delete SDM logon information (rc=0)
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlMSSendLogon: insert SDM logon information (port=50218; rc=0)
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlICheckProcessList: process server0 (pid:4684) died (RUN-FLAG)
[Thr 4512] JControlIResetProcess: reset process server0
[Thr 4512] JControlIResetProcess: [server0] not running -> increase error count (1)
[Thr 4512] JControlICheckProcessList: running flight recorder:
C:\j2sdk1.4.2_13\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID28653750 1189856249 -bz D:\usr\sap\NW2\SYS\global
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=ID28653750
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = -debugMode=yes
-> arg[15] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] JControlICheckProcessList: process server0 started (PID:3944)
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlICheckProcessList: process server0 (pid:3944) died (RUN-FLAG)
[Thr 4512] JControlIResetProcess: reset process server0
[Thr 4512] JControlIResetProcess: [server0] not running -> increase error count (2)
[Thr 4512] JControlICheckProcessList: running flight recorder:
C:\j2sdk1.4.2_13\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID28653750 1189856314 -bz D:\usr\sap\NW2\SYS\global
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=ID28653750
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = -debugMode=yes
-> arg[15] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlICheckProcessList: process server0 started (PID:4308)
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlICheckProcessList: process server0 (pid:4308) died (RUN-FLAG)
[Thr 4512] JControlIResetProcess: reset process server0
[Thr 4512] JControlIResetProcess: [server0] not running -> increase error count (3)
[Thr 4512] JControlICheckProcessList: running flight recorder:
C:\j2sdk1.4.2_13\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID28653750 1189856350 -bz D:\usr\sap\NW2\SYS\global
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=ID28653750
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = -debugMode=yes
-> arg[15] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] JControlICheckProcessList: process server0 started (PID:2616)
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlICheckProcessList: process server0 (pid:2616) died (RUN-FLAG)
[Thr 4512] JControlIResetProcess: reset process server0
[Thr 4512] JControlIResetProcess: [server0] not running -> increase error count (4)
[Thr 4512] JControlICheckProcessList: running flight recorder:
C:\j2sdk1.4.2_13\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID28653750 1189856405 -bz D:\usr\sap\NW2\SYS\global
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:10, argument:1 from pid:0
[Thr 5144] JControlIDumpStackTrace: dump stacktrace for server0
[Thr 5144] *** ERROR => Can't send command for stack dump (rc=-3) [jcntrxxi.c 1403]
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:19, argument:1 from pid:0
[Thr 5144] JControlITraceIncrement: increment trace level for server0
[Thr 5144] *** ERROR => Can't send command for trace level increment (rc=-3) [jcntrxxi.c 1434]
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:4, argument:1 from pid:0
[Thr 5144] JControlIEnableProcess: enable process server0
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=ID28653750
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = -debugMode=yes
-> arg[15] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] JControlICheckProcessList: process server0 started (PID:3556)
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlICheckProcessList: process server0 (pid:3556) died (RUN-FLAG)
[Thr 4512] JControlIResetProcess: reset process server0
[Thr 4512] JControlIResetProcess: [server0] not running -> increase error count (5)
[Thr 4512] JControlICheckProcessList: running flight recorder:
C:\j2sdk1.4.2_13\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID28653750 1189856490 -bz D:\usr\sap\NW2\SYS\global
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:4, argument:1 from pid:0
[Thr 5144] JControlIEnableProcess: enable process server0
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=ID28653750
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = -debugMode=yes
-> arg[15] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] JControlICheckProcessList: process server0 started (PID:2872)
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlICheckProcessList: process server0 (pid:2872) died (RUN-FLAG)
[Thr 4512] JControlIResetProcess: reset process server0
[Thr 4512] JControlIResetProcess: [server0] not running -> increase error count (6)
[Thr 4512] JControlICheckProcessList: running flight recorder:
C:\j2sdk1.4.2_13\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID28653750 1189858000 -bz D:\usr\sap\NW2\SYS\global
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:10, argument:1 from pid:0
[Thr 5144] JControlIDumpStackTrace: dump stacktrace for server0
[Thr 5144] *** ERROR => Can't send command for stack dump (rc=-3) [jcntrxxi.c 1403]
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:8, argument:1 from pid:0
[Thr 5144] JControlIDisableDebugging: disable debugging server0
[Thr 5144] JControlIEnableProcess: restart process server0
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:4, argument:1 from pid:0
[Thr 5144] JControlIEnableProcess: enable process server0
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=ID28653750
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] JControlICheckProcessList: process server0 started (PID:4836)
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:8, argument:1 from pid:0
[Thr 5144] JControlIDisableDebugging: disable debugging server0
[Thr 5144] JControlIEnableProcess: restart process server0
[Thr 5144] JControlIProcessSoftKill: soft kill of process server0 (pid:4836)
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:8, argument:1 from pid:0
[Thr 5144] JControlIDisableDebugging: disable debugging server0
[Thr 5144] JControlIEnableProcess: restart process server0
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:8, argument:1 from pid:0
[Thr 5144] JControlIDisableDebugging: disable debugging server0
[Thr 5144] JControlIEnableProcess: restart process server0
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlICheckProcessList: process server0 (pid:4836) died (STOPPING)
[Thr 4512] JControlIResetProcess: reset process server0
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=ID28653750
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] JControlICheckProcessList: process server0 started (PID:5428)
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlICheckProcessList: process server0 (pid:5428) died (RUN-FLAG)
[Thr 4512] JControlIResetProcess: reset process server0
[Thr 4512] JControlIResetProcess: [server0] not running -> increase error count (7)
[Thr 4512] JControlICheckProcessList: running flight recorder:
C:\j2sdk1.4.2_13\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID28653750 1189860005 -bz D:\usr\sap\NW2\SYS\global
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:8, argument:1 from pid:0
[Thr 5144] JControlIDisableDebugging: disable debugging server0
[Thr 5144] JControlIEnableProcess: restart process server0
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:4, argument:1 from pid:0
[Thr 5144] JControlIEnableProcess: enable process server0
JControlStartJLaunch: program = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[00] = D:\usr\sap\NW2\JC02\exe\jlaunch.exe
-> arg[01] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> arg[02] = -DSAPINFO=NW2_02_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=D:\usr\sap\NW2\JC02\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4516
-> arg[06] = -nodeName=ID28653750
-> arg[07] = -jvmOutFile=D:\usr\sap\NW2\JC02\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=D:\usr\sap\NW2\JC02\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=D:\usr\sap\NW2\JC02\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = pf=D:\usr\sap\NW2\SYS\profile\NW2_JC02_mmsr17
-> lib path = PATH=C:\j2sdk1.4.2_13\jre\bin\server;C:\j2sdk1.4.2_13\jre\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_13\bin;D:\usr\sap\NW2\JC02\j2ee\os_libs;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;D:\usr\sap\NW2\SYS\exe\uc\NTI386
[Thr 4512] JControlICheckProcessList: process server0 started (PID:5196)
[Thr 4512] Mon Mar 24 17:07:20 2008
[Thr 4512] JControlICheckProcessList: process server0 (pid:5196) died (RUN-FLAG)
[Thr 4512] JControlIResetProcess: reset process server0
[Thr 4512] JControlIResetProcess: [server0] not running -> increase error count (8)
[Thr 4512] JControlICheckProcessList: running flight recorder:
C:\j2sdk1.4.2_13\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID28653750 1189860117 -bz D:\usr\sap\NW2\SYS\global
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:8, argument:1 from pid:0
[Thr 5144] JControlIDisableDebugging: disable debugging server0
[Thr 5144] JControlIEnableProcess: restart process server0
[Thr 5144] Mon Mar 24 17:07:20 2008
[Thr 5144] JControlRequestFunc: receive command:8, argument:1 from pid:0
[Thr 5144] JControlIDisableDebugging: disable debugging server0
[Thr 5144] JControlIEnableProcess: restart process server0
Thanks,
VivekHi Vivek,
FYI :
JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\NW2\JC02\exe\jvmx.jar
The above message can be ignored. You will see that message often in perfectly up/running systems as well.
Also, the dev_jcontrol file shows that the server process was terminating !
You need to check std_server0.out file for the errors/exceptions as to why server0 was terminating abruptly. The reason should be apparent from dev_server0 and std_server0 most of the times unless its a startup framework bug where the error messages are not written to the log files.
So, whenever the server process or dispatcher process fails to start, you should check the corresponding dev_server<n> or dev_dispatcher and std_server<n> / std_dispatcher files. Also, usually, there will be some exception (if its application related) in the defaultrace file as well under server<n>\log or dispatcher\log depending on which one is failing to start.
e.g. if server0 is failing to start due to some UME issues, you will see the mention of it in std_server0.out (definitely) and more ellaborate info/exceptions in deafultrace under server0\log as well.
Hope the above helps. -
LabVIEW Application throws Error in Run VI Invoke node
Hi All,
We are facing an issue with an application developed from LabVIEW 2010SP1.
Application Description:
In our application, there is a top level VI which tries to run VIs dynamically[using Run VI invoke node] from a particular folder. This folder is like a plugin - not part of Exe. This implies when the top level VI is launched, the plugin VIs under particular folder will not be in memory. When we try to run a VI dynamically from the top level VI, the VI execution works perfectly in LabVIEW development mode.
Problem Faced:
When we created an EXE, it worked well in my PC [LabVIEW is installed]. We created an installer and tested in few other PCs.
[Non LabVIEW PCs – Win XP and 7]. In few PCs it throws the following error, when the plugin VI is run dynamically.
Error 1003 occurred at Invoke Node
Possible reason(s):
LabVIEW: The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located. Select File>>Open to open the VI and then verify that you are able to run it.
Method Name: Run VI
We tried the following possible ways to find the reason for the issue:
1. Installed LabVIEW - Issue got fixed.
2. Installed .net 2.0 without installing LabVIEW - Issue got fixed.
3. But in one of the Windows 7 [Non - LabVIEW PC] in which .net was already installed, we faced the same error.
Only after installing LabVIEW the error got fixed.
4. When .net 2.0 is uninstalled the EXE itself is broken.
We are not sure what is the Exact reason fo the issue. Anyone faced these kind of issues? Please share the solution. Thanks in advance.
Note:
1. The VIs which are dynamically called is a plugin and not a part of EXE.
2. These plugin VIs have no dependencies from vi library and is completely isolated.
3. We are not using any .net related objects in any of the VIs.
4. The plugin VIs use Call library function node in which a C DLL developed from Microsoft Visual Studio 2010 is used.
Thanks,
Meena
Solved!
Go to Solution.Error 1003: This clearly indicates that the 'Dynamic VI' is broken and now you should check for the various reasons, why the 'Dynamic VI' is broken.
Also path of 'Dynamic VI' is not a problem.
One thing that you may try is:
-> First open just the 'Dynamic VI' in a new LabVIEW project and check for the 'Dependencies'.
-> Now if any of the item in 'Dependencies', other than what is listed in vi.lib (lets call it 'Dependency.VI'), is also a part of your 'Main Exe', then its a problem. Because when you will execute the 'Main Exe', say in a new computer other than your development computer, it will load all its dependencies including 'Dependency.VI' (and the path will be within the 'Main Exe', but when it will try to (dynamically) load the 'Dynamic VI', this VI will also try to load the same 'Dependency.VI' but from different path and that will cause a conflict. I had experienced this.
-> If thats the issue, you may want to rename (add suffix/prefix) to all dependencies of your 'Dynamic VI' which is common to the 'Main Exe'.
Hope this solves your issue.
I am not allergic to Kudos, in fact I love Kudos.
Make your LabVIEW experience more CONVENIENT. -
Does "Run VI" invoke node work on strict references to REENTRANT VIs?
I am using LV 6.02 on Windows 2000.
I am trying to use the "Run VI" invoke node method with a reference to a Reentrant VI, with no success. (It works when VI is not reentrant. Perhaps there is a reason this cannot work. But if not, I wonder if there is a workaround, or if LabVIEW 6.1 has a fix?
Hopefully the picture of the block diagram I included is sufficient...but I also included the actual code just in case.
Thanks!
Steve
Attachments:
block_diagram.jpg 66 KB
Parent_VI_Example.vi 43 KB
Prototype_subVI_shell_for_Simplex_Fit.vi 40 KBHi, Labviewguru,
Thanks for taking the time to look at my admittedly messy (flawed) block diagram. I will try to state my ultimate goal:
You may be familiar with Levinberg-Marquardt nonlinear curve fit in Labview, which is about 5 VIs in a LLB file. In order to change the type of curve fitting, one has to either modify a formula node in the lowest subVI (Target Func and Deriv), or place a different subVI in there. That's fine until I want to have many different sorts of algorithms.
What I was thinking of doing is instead passing Target Func and Deriv a reference to the VI which would perform the calculations. This would allow me to use the same fitting code to fit different types of data with substantially different methods--without modifyin
g the low-level fitting code at all.
I'm not sure this is going to make any sense to you, but thanks again for your help.
In regards to your answer above, let me clarify somewhat. I had the call by reference node in there to prove that the reference to the VI was "good" and worked fine...this same reference was passed to the invoke node, which didn't have any apparent effect.
Also, I don't think the path to the VI I am opening the reference to is redundant. It is required to tell the "Open VI reference" which VI to load.
I agree that using references to pass values around is not generally a good idea: I was using that method for my supposed versatility in the future.
Thanks,
Steve -
Document() not returning a useable node set?
If I open another document during a transform, I can dump out the file using
xsl:message, but can't match any tags in the loaded file. If I replace the Sun
implementation with the apache implementation of xalan with -Xbootclasspath/p,
the code runs fine.
Example fragment:
<xsl:variable name="user_type">
<xsl:for-each select="//include/@file_name">
<xsl:variable name="xmlFile">
<xsl:value-of select="$xml_dir"/>/<xsl:value-of select="."/>
</xsl:variable>
<xsl:for-each select="document($xmlFile)" >
<xsl:value-of select="key('type_def_key',$datatype)//datatype" />
</xsl:for-each>
</xsl:for-each>
</xsl:variable>
<xsl:message>
User type <xsl:value-of select="$user_type" /> for <xsl:value-of select="$datatype" />
</xsl:message>
I believe the problem is with the document function not returning a useable
node set , or all of the matches are going back to the original document rather
than the one that was just open. With in the context of the new document
select="." appears to work, but nothing else seems to.
Output using Sun's xml implementation (JDK 5.0, 6.0 snapshot)
User type for Gms_User_Id
Output using the Apache xml implmentation (Xalan 2.6)
User type numeric for Gms_User_Id
The code and xml files are the same in both cases, just changed the runtime
class path withThis is behaving as designed.
Configuring a view object so expect certain entity subtypes does not automatically restrict the rows it queries. If the view object's query returns any row that has a discriminator value that does not match the design-time configured entity subtypes expected, it is not added to the result rowset.
If you have limited the number of fetched rows to 1, and if that row had a discriminator attribute value that does not match that/those of the expected entity subtypes, then the single row returned by the query will not be added to the result rowset. The result is that the row set has zero rows in it.
Maybe you are looking for
-
Can I use my Apple Keyboard in a non-bootcamp Windows 7 OS?
Hello, I am building myself a secondary gaming PC to complement my Mac Pro (which I will continue to work on) but would like to 'reuse' my Apple Keyboard that I like so much. From running Windows 7 in bootcamp on my current Mac Pro I know that the ke
-
The welcome screen always appears upon starting iTunes. (Win7 with newest iTunes update)
The only option to get past is to click either "Agree" or "No thanks" and then I can view my music. However, upon closing and re-opening, the same screen will show up. Very annoying.
-
Account grouping/Transaction keys PRD/DIF
Hello Gurus I have a situation that some MIRO posting are using PRD and some are using DIF transaction keys. For some reason The postings with DIF are not picking up the material thus resulting in putting dummy profit center. Please advise the diffe
-
HRPY - Problem with upload payroll
Hi experts I need your help, I have a problem and I can't resolve. In my job I need to move the payroll from a country (BR) to another country (MX), Each country is in different client. To download the data from BR, I used the fm HCRM_PAYROLL_RESULTS
-
How can i find my ipod with serial nuber and plz dont tell me nooo iyts not possible
helpp