Bug? Cannot export shared variable, if it's in a virtual folder within an .lvlib

Hello,
I was trying to keep my libary of shared variables organized by categorizing the variables into different virtual folders. However, it turns out that variables in virtual folders are excluded from exports, even though they (and their folders) are visible in the Multiple Variable Editor.
Is this by design (in LabVIEW 2012)? If so, what's the rationale?
Thanks!

Hi,
When there are variables inside nested virtual folders within a Library, the multiple variable editor does not work. If you select several variables in a virtual folder and right-click and select Multiple variable editor, the editor opens but you cannot change anything.
Workaround: Convert folders to libraries or move variables under a single folder.
Regards,

Similar Messages

Vestigial fields when exporting shared variables

Hello,
Is this a bug? I have a network-published shared variable that used to have aliasing enabled. After I cleared the "Bind to:" field and disabled aliasing, I exported its library into CSV mode. However, it still contained the columns (among others):
NetworkrojectBinding = TRUE
NetworkrojectPath = <old variable that it was bound to>
The extra columns messed up my CSV parser. The only way I could find to prevent their appearance was to delete all the variables that used to have project binding, and re-create them

JKSH,
I was able to reproduce the same issue here. I'll look into this a little more and see if this may in fact be a bug.
James K.
National Instruments
Applications Engineer

Exporting Shared Variables to csv

When I try and export SV information to csv, LV (2009, DSC) doesn't seem to recognize any variables that are located within virtual folders in the library. Does anyone know a work-around to get that data tabulated short of cycling through the whole library writing values from SharedVariableIO property nodes to file?
Thanks,
Kyle
CLD using LV, DSC 8.5-2009, RT 8.5
Ghoti!

muks wrote:
Have you seen this?
Yep. That's the problem. The shared variable library I'm working with contains well over 1000 variables that are organized into a few dozen virtual folders within the library. When I use the Export Variables function you linked to, it doesn't "see" any variables in folders, only those in the library root.
CLD using LV, DSC 8.5-2009, RT 8.5
Ghoti!

CR XI R3: Issue exporting shared variable to Excel - with workaround

Hi,
I have a report that uses a subreport to calculate a field based on the existance (or not) of data in a database other than the main report database. When I use a shared variable to pass this field back to the main report and display it on a detail line (in the main report), it works fine - until I try to export the report to Excel. When exported, the value that gets exported on all detail lines of the report is the final non-blank value of the shared variable, not the value that it contained when the detail line was initially generated. I am using a shared variable because there are multiple values that I want to pass back to the main report.
Luckily, only one of the shared variables are being printed, so the workaround that I am using is to use the subreport to print the field instead of passing the value back in a shared variable and displaying that (and hiding the subreport on a separate format).
Is this a known issue with R3 exporting to Excel? (It was happening in R2 as well...)
HTH,
Carl

Simplified somewhat, what this report is doing is looking up open orders in one database and checking to see if something specific happened to it in another database. If so, it generates the XML that needs to be applied to the first database to update it. The XML references the order number and line number. What I mean is that instead of the data coming out as
Order Line XML Snippet
12345 1234 ...<order>12345</order><line>1234</line><status>received</status>...
22345 2234 ...<order>22345</order><line>2234</line><status>received</status>...
32345 3234 ...<order>32345</order><line>3234</line><status>received</status>...
42345 4234 ...<order>42345</order><line>4234</line><status>received</status>...
I get
Order Line XML Snippet
12345 1234 ...<order>42345</order><line>4234</line><status>received</status>...
22345 2234 ...<order>42345</order><line>4234</line><status>received</status>...
32345 3234 ...<order>42345</order><line>4234</line><status>received</status>...
42345 4234 ...<order>42345</order><line>4234</line><status>received</status>...
I have Base Column Widths on Details, so there should be no merging attempted, but I'll check and make sure.
It seems to me, though, that the DLL is being told the wrong value to export...
Carl

VI cannot find shared variable in engine despite successful deployment

I am unable to use Shared Variables to communicate between VIs located on my PC and the VIs located on my cRIO-9014. This is a new development as I have been running the same VIs for over a year without this problem. The only recent development is that the IT department at my company installed new virus protection software and changed some windows firewall settings on the PC that I am using. This problem first began as soon as I got the PC back from IT. I have since unblocked LabView in Windows Firewall but that has not fixed the problem. The error I get every time I try to read a shared variable on the real time target is:
Error -1950679035 occurred at Shared Variable Read in RT Interface.vi
Possible reason(s):
LabVIEW: (Hex 0x8BBB0005) Unable to locate variable in the Shared Variable Engine. Deployment of this variable may have failed.
I have redeployed all of my shared variables and according to LabView the deployment was successful, yet I still get this error every time. Is it likely that something the IT department did with the Antivirus/Firewall software has blocked communication between the cRIO-9014 and my PC? I have used Measurement & Automation Explorer to check communication with the device and as far as I can tell everything seems fine.

After adding LabVIEW to the exceptions list of Windows Firewall, my issue seemed to be cleared up. I am now getting the same error message once again, but now I get it every time I run a VI with shared variables and it actually pops up an error message asking me to continue or stop. Again, according to LabVIEW the shared variables deployed successfully. I looked at the two KB articles that were posted and it seemed like this error has three causes:
1-Unsuccessful deployment - everything seems to have deployed
2-Firewall Issues - were taken care of to fix my original problem
3-Shared Variable Engine not running
I've looked around and I found a reference to 'repairing' the shared variable engine but not a guide for how to do that. I have opened variable manager (I am using LabVIEW 8.5) and have stopped and started the shared variable engine with no effect.
What are steps I can take to ensure the Shared Variable engine is running properly?

Support for Shared Variables in Third Party XP embedded based TPC's?

I have deployed an application in an XP embedded based Touch Panel (Third party). The application is working fine, but the shared variables hosted on an RT (sbRIO Board) are not getting updated in the application on TPC
1. The TPC is part of the project as Windows XP Embedded Touch Panel
2. NI TPC Service has been installed on the TPC and the application can be deployed remotely from the development PC through ethernet. (Hence network connections and communications are OK)
3. By using Distributed Systems Manager in the development computer, I can see that the shared variables are getting updated on the network
I believe that the problem can be solved if the following programs are installed on the TPC
A. Support for shared variables for XPembedded
B. Shared Variable engine
I have tried installing support for shared variables from Program Files > National Instruments > Labview 8.6 > PDA > Utilities > Variables > x86 - but am getting an installation error "Unable to find application manager for Pocket PC applications".
Shared variable engine has been installed from ve220 folder. The program is getting installed. But the Variable Engine is not started Control Panel > Administrative tools > Services in Xpe, the service is stopped and cannot be started. When I try to start the service, I am getting the following error on TPC
"Could not start the National Instruments Variable Engine Service on the local computer.
Error 1053. The service did not respond to the start or control request in a timely fashion."
Please suggest solutions for the above or alternate locations for the following:
1. Support for shared variables for XP embedded TPC's
2. Shared Variable engine installer program.
Thanks
Krish
Solved!
Go to Solution.

Problem solved!
Update for interested folks working on XP Embedded TPC's
Just to make sure that Shared Variables were indeed accessible to the TPC, I wanted to install Distributed Systems Manager 8.6 on the TPC. However since the TPC was having only 1 GB of DOM (Disk on Memory) and with all the software I had tried, there were only a few Megabytes left on the system. I had to add another DOM of 2 GB.
All the products of the Installation went fine, with the exception of NI Logos (Version 5.0). NI Logos installation failed repeatedly. I tried installing NI Logos separately, with the same results. Then I had this gut feeling that NI Logos had something to do with the issue.
I then downloaded the new version of NI DSM 2009 SP1. Although this was supposed to get installed on any fresh system without Labview, the installation would not proceed beyond the setup stage. I tried installing NI Logos from the products folder on the new download separately and it worked like magic!
Once the new Logos (Ver 5.5) got installed, the Shared Variable Engine started automatically and the Shared Variables were finally unleashed - free to rise and shine! Thank God Almighty!!
On the lighter side, come to think of it - for running an application of around 400KB, we need XP embedded, NI Run Time, Logos, DSM .......... (all around 900MB). Can we make it any simpler?!! Inviting your comments .......
Thanks
Krish

How do I setup shared variables between executables created in sepparate projects

Hello,
I have several sepparate projects with their own respective executable files and I would like to be able for these executable files to all share the same variable (one program controls the value of the variable, while the others read from it).
I got this setup to work on my personal computer (by being able to access variable manager, etc), but I need to deploy these executables on different computers that don't have the labview development program. What steps do I need to do in order for me to be able to put these executables on any computer (I'm assuming I need to setup a path for the shared variable that is always in the same folder, etc)
Thanks
Vlad
Solved!
Go to Solution.

Hi Vlad,
I think this article may answer some of your questions regarding shared variables in deployed applications.
http://zone.ni.com/devzone/cda/tut/p/id/9900
It sounds like you already have your executables built, but this article may answer some questions about deploying them to other machines.
http://zone.ni.com/devzone/cda/tut/p/id/3303
Jeff S.
National Instruments

Shared Variable Deployment not accessible in Build Specification

Hi everyone,
I have a large project developed in LV 8.6.1 from which I executed numerous applications. I converted the project in LV 11 sp1f1, everything works well in code, everything is saved.
I wanted to build executable without cod change for LV 11 here is what I found:
Build the executable with Build Specifications inherited from LV 8.6 for which I checked on Use Labview 8.x file layout in Advanced. My application programmatically deploys all internal shared variables and when I wanted to access the Shared Variable Deployment in project in Build Specification then labview locked and I have to kill LV. Other time I did not access the Shared Variable Deployment and I start building executable when it looks the build progressing similar as in LV8.6 and last step before popping the attached error all the saved files in the build location were deleted.
I set up a build specification just for this LV 11. Again I wanted to access the Shared Variable Deployment and again labview is looping something from which I had to kill labview. I opened it again, I skipped the shared variable deployment line and I build the application. Because my application programmatically deploys shared variables I included in builder the lvlib where shared variables belong. The build files does not includes this time as output the file *.lvlib for which my inherited LV8.6 code programmatic deploys shared variables.
My question is should I change the code (very large code) taking out the programmatic variables deployment and to relay on the build executable to do deploy them then what should I do with Shared Variable Deployment line in Build Specification which for my large application is not accessible or is any way to still use the shared variable as in LV8.6 but for which I need *.lvlib in build location.
Another important issue: when I launched my application built as I showed in previous second case, first thing that I see is that my application is not able to save errors (I have a log file where I save different drivers or communication errors). Any idea why application even without shared variable deployed is not able to write a text file? I am administrator of my computer with all rights.
Thank you,
Virginia

No, I am not able to close Labview because of the windows error with only one button to close application. The application is correct executed. Next time when I start this project it is asking me if I want o recover even if I accept to recover it looks what I had last time it does not save.
For my application also I am building a VI without diagram built as source distribution for which I set in my builder this top vi and I excluded everything from the project because my application copies instances at the run time of this vi as many times as hardware modules I have in the system and also I have this vi included in my application (for the content of this vi). My vi contains interfaces for hardware configuration as well as drivers functions call for each hardware module I have to control in my application. Everything is good building this vi, but in less then one minute after the build is executed and build interface closes again I have the windows error which force me to close project. Next time when I open project I did not see the option to recover the project.
In the mean time I received second message and I wonder if you refer to files names or to folder names or all together. I checked and the maximum size is 122 characters in the vi paths.
Thank you,
Virginia

Network Shared Variable: Aliasing not working

Hello!
I am running a cRIO 9075, which is publishing network shared variables.
I can see and modify them within Distributed System Manager.
Unfortunately I am not able to read/write the variables through labview.
What I have done so far:
Tools -> Shared Variable -> Register Computer, using the IP of the cRIO
Adding a Variable to the project. Type = Network-Published, Enable Aliasing, choosing "Browse" to select the variable (all published variables from cRIO are shown there), Access Type = read/write. The PSP-URL is: \\192.168.10.70\WaveformManager\Op
Trying to read the variable results code -1950679034 and the result is always the default value for that data type.
BUT this works: using the VIs Data Communication / Shared Variable / Read/Write Variable and typing in the same URL the Distributed System Manager is showing is showing (in my case: \\192.168.10.70\WaveformManager\Op)
So, what am I doing wrong? Did I forget something or misunderstand how "Aliasing" works?
Thanks!

hi,
in which way to you read your shared variable? If you read it before you write a value "into" the variable it may couse this waring.
Have you tried this?
http://digital.ni.com/public.nsf/allkb/7DBC2C3E95AFD85C86257442005CF74C?OpenDocument

Shared variable bug

Hello all:
With the attached project, run the shared variable bug.vi and press the button labeled Press me First. Then press the button labeled Press me Second. On both string indicators there shoud be text that say Hi There! in both string indicators. However, sometimes I only get only a Hi OR There! (did I say OR ) and sometimes and empty string for both itring indicator outputs.
Note this only happens when you FIRST run the VI. To repeat the bug, you will have to stop the VI and unload it from memory.
Can somebody else confirm this behavior? If confirmed, this is obviously a bug.
Robert
Attachments:
Shared Variable Bug.zip ‏25 KB

There seems to be some sort of latency when you read the value of the shared variable. I took your example, but I moved the read of the shared var. outside of the loop. After the first boolean is pressed, it took two loop iterations ~100 mS for the shared variable value (read) to update.
"There is a God shaped vacuum in the heart of every man which cannot be filled by any created thing, but only by God, the Creator, made known through Jesus." - Blaise Pascal
Attachments:
Shared Variable Bug.vi ‏44 KB

FCPX Export issue. Item cannot be shared while it is still referencing media on the camera

I am having issues with exporting a project I just shot and I missed my delivery day and am now late. Need help ASAP. I'll try to keep this as brief as possible and stick to the pertinent information.
The Shoot: -2 Panasonic HVX-200's shooting on P2 Media shooting a live event -Dumped footage onto external hard drive via Macbook Pro on set into separate folders for organization using a Panasonic P2 Reader. -All dumps were confirmed completed and all footage accounted for.
The System: -Using Final Cut Pro X 10.1.2 -Mac Pro Tower 2009 quad core running OSX Mavericks 16gb Ram -Blackmagic Intensity Pro Card
The Edit: -2 Camera multicam edit -Imported footage using import media function -Imported from external drive -(important note: a camera has never been connected to the computer for this project) -Edit is finished, about a 2hr 20 min finished sequence (live event 2 cameras switched in post, all graphics and everything is done)
The Problem: -When I go to export via the "Share" function i get an error that says "This Item cannot be shared while it is still referencing media on the camera" -Imported footage has the camera logo in the corner meaning that it is referencing camera media; yet no camera has ever been connected.
Solutions I have tried: -Re-importing media with re-import function --Says that the camera is not connected yet I never had one connected in the first place. -Deleting preferences -Biting the bullet and starting from scratch to do a re-edit -- footage will not import without referencing "camera media" -Tried importing via dragging and dropping. Says it cannot importing the following files, lists all of the XML and MXF files -Started a new event, with a new project, with a fresh import; same results -Googled this to death, no solution seems to work, but I'll try whatever I have to; client needs this ASAP.
Questions: -The external drive is not showing up as a camera, so why is it importing as camera media? -Is there a way to salvage my edit and get it exported? I have a lot of hours into this and quite frankly, no time to redo the whole thing.
Please help!

I have had this issue too, and figured a work around. FYI, I rebooted, tried everything imaginable, and still no luck. I opened up iPhoto, and imported all the video clips into iPhoto. I then took the missing video from iPhoto, copied it to my desktop. Then I re-imported the video (same name) into Final Cut. I had to do some slight editing of the video, but everything worked fine, and allowed me to upload the video to YouTube.
Not certain it will work for others, but to recap, try to import the video into another program, then copy the missing video file to your desktop, and re-import to Final Cut.
Hope this helps.

Dsc 8.2.1 cannot write to shared variables error 1950679035

I am getting error 1950679035 ni_tagger_write when I try to write to my shared variables. I recently upgraded from labview 8.2 to 8.2.1. I also upgraded to DSC 8.2.1. During the install, I had to upgrade my computer to SP2 (windows xp), which installed mdac 2.8 sp1 for use with dsc 8.2.1.
I have the windows firewall turned off, I checked with our IT dept and no upgrades were completed overnight (as the program worked yesterday using 8.2). I checked and MAX will get a connection with the fieldpoint unit. Everything is deployed from my machine, currently running under the dev environment.
I have looked at this thread, but I was not able to get anywhere, http://digital.ni.com/public.nsf/websearch/0D7B86F4B4D19A5E86256F9A006EECB1?OpenDocument and here.
Even though I have windows firewall turned off, I added all of the execptions to the windows firewall list.
It appears that the shared variable library is deploying correctly, as the the windows says that it has (when you run a vi). I am progmatically deploying the vi.
I looked at the variable manager and I attached a screenshot below. I am not sure if that means that it did not deploy correctly or not.?? (I was only watching a couple of the variables, I have about 20 total)
thanks
Kenny
Attachments:
variable manager.jpg ‏55 KB

It appears that my problem has been solved. Apparently our network had an internal error for a quick second and my nic did not like it. So after I restarted again (fourth of the morning) it started working now.
Kenny

Bug: Built Real-Time app won't run if it accesses a typedef'ed shared variable node

Hello,
I finished developing a Real-Time program that uses typedef'ed (clusters and enums) networked shared variables (SVs). It works fine when I run the program in Development mode. However, when I built and deployed it as a start-up app, it refuses to start. The VI monitor in the Distributed System Manager says that the VIs that use those SV nodes (and the top-level VI that references them) have "Bad" status, and the rest are "Idle".
To get my built program to run, I had to disconnect all the variables from the typedefs. Deleting the SV nodes made the program run too, but that's not an option.
Has anyone else encountered this?
Platform: LabVIEW 2012 (32-bit), NI cRIO-9076

Yes. See the following thread.
Paolo
LV 7.0, 7.1, 8.0.1, 2011

Shared Variables - Properties

Hello,
I have a couple of questions about properties of Shared Variables (SV). They can be configured either by using the dialog box (right-click on SV -> Properties), or programmatically via the "SharedVariableIO" property node. Have a look at the NI-Examples to see how SV can be created programmatically by using the DSC module.
1) The dialog box offers a property "Variable Type" which can be "Network-published", "Single-Process" or "Time-Triggered". The "SharedVariableIO" property node gives no access to this property. Does anybody know why? The same question can be rephrased: How can I create a "Single-Process" SV programmatically?
2) The "SharedVariableIO" property node has two items, "Network.OnScan" and "Network.ConnectionType", which have no direct correspondance to any of the properties available in the dialog box. What is the exact meaning of those properties? The on-line help isn't of much use here...
3) Mutliple SV can be edited by using the Multiple Variable Editor (Tools->Shared Varaible->Multiple Variable Editor). A cool feature is the import/export of CSV-files. I am interested in programmatically creating SVs from the information stored in such a CSV-file. Reading the file is no problem, but connecting the file entries to the properties of the "SharedVariableIO" property node would be quite some job. In principle NI has already solved that within the Multiple Variable Editor. I guess there is a bunch of VIs somewhere below "....Program Files/NI/.../vi.lib that do exactly this thing. Does anybody know, if these (which ones?) are available for public use?
Regards,
Dietrich

dietrich wrote:
1) The dialog box offers a property "Variable Type" which can be "Network-published", "Single-Process" or "Time-Triggered". The "SharedVariableIO" property node gives no access to this property. Does anybody know why? The same question can be rephrased: How can I create a "Single-Process" SV programmatically?
You can't. The single-process shared variable is an old style LabVIEW global placed under the shared variable abstraction. There is currently no way to create those on the fly. Time-triggered also cannot be created programmatically. I confess I don't know enough about them to know the reason why.
dietrich wrote:
2) The "SharedVariableIO" property node has two items, "Network.OnScan" and "Network.ConnectionType", which have no direct correspondance to any of the properties available in the dialog box. What is the exact meaning of those properties? The on-line help isn't of much use here...
Network.On Scan = read/write hardware? - this allows you to programmatically control when you are reading from or writing to configured hardware.
Network.ConnectionType = connect to hardware even when no one is viewing me? - this has 2 choices, UpFront & OnDemand, UpFront means that the variable will be connected to hardware even when no one is connected to the variable. This is useful when you want to reserve hardware or when logging is enabled. OnDemand means that you disconnect from hardware whenever no one is reading the variable.
dietrich wrote:
3) Mutliple SV can be edited by using the Multiple Variable Editor (Tools->Shared Varaible->Multiple Variable Editor). A cool feature is the import/export of CSV-files. I am interested in programmatically creating SVs from the information stored in such a CSV-file. Reading the file is no problem, but connecting the file entries to the properties of the "SharedVariableIO" property node would be quite some job. In principle NI has already solved that within the Multiple Variable Editor. I guess there is a bunch of VIs somewhere below "....Program Files/NI/.../vi.lib that do exactly this thing. Does anybody know, if these (which ones?) are available for public use?
I would advise against using any of these. National Instruments can change, or remove, those underlying files at any time as a result of modifications to the MVE. That could cause issues for any code using those sub-VIs.
Regards,
Robert

Error 0(Native: listNetInterfaces:[3]) and error while loading shared libraries: libpthread.so.0: cannot open shared object file: No such file or directory

Hi Gurus,
I'm trying to upgrade my test 9.2.0.8 rac to 10.1 rac. I cannot upgrade to 10.2 because of RAM limitations on my test RAC. 10.1 Clusterware software was successfully installed and the daemons are up with OCR and voting disk created. Then during the installation of RAC software at the end, root.sh needs to be run. When I run root.sh, it gave the error: while loading shared libraries: libpthread.so.0: cannot open shared object file: No such file or directory. I have libpthread.so.0 in /lib. I looked up on metalink and found Doc ID: 414163.1 . I unset the LD_ASSUME_KERNEL in vipca (unsetting of LD_ASSUME_KERNEL was not required in srvctl because there was no LD_ASSUME_KERNEL in srvctl). Then I tried to run vipca manually. I receive the following error: Error 0(Native: listNetInterfaces:[3]). I'm able to see xclock and xeyes. So its not a problem with x.
OS: OEL5 32 bit
oifcfg iflist
eth0 192.168.2.0
eth1 10.0.0.0
oifcfg getif
eth1 10.0.0.0 global cluster_interconnect
eth1 10.1.1.0 global cluster_interconnect
eth0 192.168.2.0 global public
cat /etc/hosts
192.168.2.3 sunny1pub.ezhome.com sunny1pub
192.168.2.4 sunny2pub.ezhome.com sunny2pub
192.168.2.33 sunny1vip.ezhome.com sunny1vip
192.168.2.44 sunny2vip.ezhome.com sunny2vip
10.1.1.1 sunny1prv.ezhome.com sunny1prv
10.1.1.2 sunny2prv.ezhome.com sunny2prv
My questions are:
should ping on sunny1vip and sunny2vip be already working? As of now they dont work.
if you look at oifcfg getif, I initially had eth1 10.0.0.0 global cluster_interconnect,eth0 192.168.2.0 global public then I created eth1 10.1.1.0 global cluster_interconnect with setif. Should it be 10.1.1.0 or 10.0.0.0. I looked at the subnet calculator and it says for 10.1.1.1, 10.0.0.0 is the subnet. In metalink they had used 10.10.10.0 and hence I used 10.1.1.0
Any ideas on resolving this issue would be very much appreciated. I had been searching on oracle forums, google, metalink but all of them refer to DOC Id 414163.1 but it does n't seem to work. Please help. Thanks in advance.
Edited by: ayyappa on Aug 20, 2009 10:13 AM
Edited by: ayyappa on Aug 20, 2009 10:14 AM
Edited by: ayyappa on Aug 20, 2009 10:15 AM

a step forward towards resolution but i need some help from the gurus.
root# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6
192.168.2.3 sunny1pub.ezhome.com sunny1pub
192.168.2.4 sunny2pub.ezhome.com sunny2pub
10.1.1.1 sunny1prv.ezhome.com sunny1prv
10.1.1.2 sunny2prv.ezhome.com sunny2prv
192.168.2.33 sunny1vip.ezhome.com sunny1vip
192.168.2.44 sunny2vip.ezhome.com sunny2vip
root# /u01/app/oracle/product/crs/bin/oifcfg iflist
eth1 10.0.0.0
eth0 192.168.2.0
root# /u01/app/oracle/product/crs/bin/oifcfg getif
eth1 10.0.0.0 global cluster_interconnect
eth0 191.168.2.0 global public
root# /u01/app/oracle/product/10.1.0/Db_1/bin/srvctl config nodeapps -n sunny1pub -a
****ORACLE_HOME environment variable not set!
ORACLE_HOME should be set to the main directory that contain oracle products. set and export ORACLE_HOME, then re-run.
root# export ORACLE_BASE=/u01/app/oracle
root# export ORACLE_HOME=/u01/app/oracle/product/10.1.0/Db_1
root# export ORA_CRS_HOME=/u01/app/oracle/product/crs
root# export PATH=$PATH:$ORACLE_HOME/bin
root# /u01/app/oracle/product/10.1.0/Db_1/bin/srvctl config nodeapps -n sunny1pub -a
VIP does not exist.
root# /u01/app/oracle/product/10.1.0/Db_1/bin/srvctl add nodeapps -n sunny1pub -o $ORACLE_HOME -A 192.168.2.33/255.255.255.0
root# /u01/app/oracle/product/10.1.0/Db_1/bin/srvctl add nodeapps -n sunny2pub -o $ORACLE_HOME -A 192.168.2.44/255.255.255.0
root# /u01/app/oracle/product/10.1.0/Db_1/bin/srvctl config nodeapps -n sunny1pub -a
VIP exists.: sunny1vip.ezhome.com/192.168.2.33/255.255.255.0
root# /u01/app/oracle/product/10.1.0/Db_1/bin/srvctl config nodeapps -n sunny2pub -a
VIP exists.: sunny2vip.ezhome.com/192.168.2.44/255.255.255.0
Once I execute the add nodeapps command as root on node 1, I was able to get vip exists for config nodeapps on node 2. The above 2 statements resulted me with same values on both nodes. After this I executed root.sh on both nodes, I did not receive any errors. It said CRS resources are already configured.
My questions to the gurus are as follows:
Should ping on vip work? It does not work now.
srvctl status nodeapps -n sunny1pub(same result for sunny2pub)
VIP is not running on node: sunny1pub
GSD is not running on node: sunny1pub
PRKO-2016 : Error in checking condition of listener on node: sunny1pub
ONS daemon is not running on node: sunny1pub
[root@sunny1pub ~]# /u01/app/oracle/product/crs/bin/crs_stat -t
Name Type Target State Host
ora....pub.gsd application OFFLINE OFFLINE
ora....pub.ons application OFFLINE OFFLINE
ora....pub.vip application OFFLINE OFFLINE
ora....pub.gsd application OFFLINE OFFLINE
ora....pub.ons application OFFLINE OFFLINE
ora....pub.vip application OFFLINE OFFLINE
Will crs_stat and srvctl status nodeapps -n sunny1pub work after I upgrade my database or should they be working now already? I just choose to install 10.1.0.3 software and after running root.sh on both nodes, I clicked ok and then the End of installation screen appeared. Under installed products, I see 9i home, 10g home, crs home. Under 10g home and crs home, I see cluster nodes(sunny1pub and sunny2pub) So it looks like the 10g software is installed.

Bug? Cannot export shared variable, if it's in a virtual folder within an .lvlib

Similar Messages

Maybe you are looking for