Unable to start DSC Shared Memory

I am running LabView 7.0 (I know its an older setup), with DSC and Lookout OPC to do Serial communications to an Omron PLC. I needed to update the Ni-DAQ because the PCI-6220 board needs the driver. I upgraded to NI-DAQ 7.5 and now a get the Unable to start the DSC Shared Memory Manager Service. I have uninstalled the DSC and reinstalled it with no change. I found in the discussion boards that I need nidscsm.exe in the windows\system32 folder but it is not there. I am running Windows XP.
I have 2 setups like this. 1 PC still connects to the PLC even though the error pops up, another PC will not connect at all, lights blink but then comms timeout error.
Thanks!
Solved!
Go to Solution.

NI DAQ is now out of date, if possible you should use DAQmx instead. According to this chart, you can use any version before DAQmx 8.1. This new driver should work better with DSC. If you need some help converting your code check out this tutorial:Transition from Traditional NI-DAQ to NI-DAQmx in LabVIEW

Similar Messages

Unable allocate bytes of shared memory

When I execute the sql statement in sql*plus,I find the error:
ORA-04031:unable to allocate 618744 bytes of shared memory
("shared pool","unknown object","cursor work he","kllcqc,kllcqslt")
I query the performance view 'v$sgastat',free memory in shared pool
is 200399720 bytes.
why?how should I do?

What is the version of Oracle you are running. If you are running Oracle 8.1.7 on Sun OS, apply the relevant patch. This problem will vanish.

Ora- shared memory segment

Hello, gurus!
I can connect this way:
oracle@mypc sqlplus sys/sys1@mydatabase
While trying to connect this way:
oracle@mypc sqlplus sys/sys1
I am getting an error:
ORA-01034: Oracle not available
ORA-27123: unable to attach to shared memory segment
Linux Error: 13 permission denied
What's wrong?
I am on LINUX RHEL 4 + Oracle 10.2.0.4
Thanks in advance.

user21123, the init.ora and/or spfile have nothing to do with this issue. These errors means that you are attempting to connect to an Oracle instance that cannot be located. This can be because you have an environment error setting as the first response mentioned or before the target instance is not running as I mentioned.
Here is the error when the environment variables are set correctly but the database is not started.
JServer Release 9.2.0.6.0 - Production
$ print $ORACLE_SID $TWO_TASK
TRN1
$ sqlplus mpowel01
SQL*Plus: Release 9.2.0.6.0 - Production on Fri Aug 22 13:07:48 2008
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Enter password:
ERROR:
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
IBM AIX RISC System/6000 Error: 2: No such file or directory
SP2-0157: unable to CONNECT to ORACLE after 3 attempts, exiting SQL*Plus
$ sqlplus /nolog
SQL*Plus: Release 9.2.0.6.0 - Production on Fri Aug 22 13:08:24 2008
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
> connect / as sysdba
Connected to an idle instance.
> startup
ORACLE instance started.
Total System Global Area 114468624 bytes
<snip>
> exit
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.6.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP and Oracle Data Mining options
JServer Release 9.2.0.6.0 - Production
$ sqlplus mpowel01
SQL*Plus: Release 9.2.0.6.0 - Production on Fri Aug 22 13:11:58 2008
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Enter password:
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.6.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP and Oracle Data Mining options
JServer Release 9.2.0.6.0 - Production
TRN1 >HTH -- Mark D Powell --

Cannot attach data store shared-memory segment using JDBC (TT0837)

I'm currently evaluating TimesTen during which I've encountered some problems.
All of the sudden my small Java app fails to connect to the TT data source.
Though I can still connect to the data source using ttisql.
Everything worked without problems until I started poking around in the ODBC administrator (Windows 2K).
I wanted to increase permanent data size so I changed some of the parameters.
After that my Java app fails to connect with the following message:
DriverManager.getConnection("jdbc:timesten:direct:dsn=rundata_tt60;OverWrite=0;threadsafe=1;durablecommits=0")
trying driver[className=com.timesten.jdbc.TimesTenDriver,com.timesten.jdbc.TimesTenDriver@addbf1]
SQLException: SQLState(08001) vendor code(837)
java.sql.SQLException: [TimesTen][TimesTen 6.0.4 ODBC Driver][TimesTen]TT0837: Cannot attach data store shared-memory segment, error 8 -- file "db.c", lineno 8846, procedure "sbDbConnect()"
The TT manual hasn't really provided any good explanation what the error code means.
Obviusly I'v already tried restoring the original ODBC parameters without any luck.
Ideas..anyone?
/Peter

Peter,
Not sure if you have resolved this issue or not. In any case, here are some information to look into.
- On Windows 32-bit, the allocation of shared data segment doesn't work the same way like on Unix and Linux. As a result, the maximum TimesTen database size one can allocate is much smaller on the Windows platform than on other platforms.
- Windows error 8 means ERROR_NOT_ENOUGH_MEMORY: not enough storage is available to process this command.
- TimesTen TT0837 says the system was unable to attach a shared memory segment during a data store creation or data store connection operation.
- What was the largest successful perm-size and temp-size you used when allocating the TimesTen database?
* One explanation for why you were able to connect using ttIsql is that it doesn't use much of the DLLs, whereas your Java application typically has a lot more DLLs.
* As a troubleshooting step, you can try reduce your Temp-size to a very small size and just see if you can connect to the data store. Eventually, you may need to reduce your perm-size to get Windows to fit the shared data segment in the process space.
By the way the TimesTen documentation has been modified to document this error as follows:
Unable to attach to a shared memory segment during a data store creation or data store connection operation.
You will receive this error if a process cannot attach to the shared memory segment for the data store.
On UNIX or Linux systems, the shmat call can fail due to one of:
- The application does not have access to the shared memory segment. In this case the system error code is EACCESS.
- The system cannot allocate memory to keep track of the allocation, or there is not enough data space to fit the segment. In this case the system error code is ENOMEM.
- The attach exceeds the system limit on the number of shared memory segments for the process. In this case the system error code is EMFILE.
It is possible that some UNIX or Linux systems will have additional possible causes for the error. The shmat man page lists the possibilities.
On Windows systems, the error could occur because of one of these reasons:
- Access denied
- The system has no handles available.
- The segment cannot be fit into the data section
Hope this helps.
-scheung

Error message: ORA-27125: unable to create shared memory segment Linux-x86_

Hi,
I am doing an installtion of SAP Netweaver 2004s SR3 on SusE Linux 11/Oracle 10.2
But i am facing the follow issue in Create Database phase of SAPInst.
An error occurred while processing service SAP NetWeaver 7.0 Support Release 3 > SAP Systems > Oracle > Central System > Central System( Last error reported by the step :Caught ESAPinstException in Modulecall: ORA-27125: unable to create shared memory segment Linux-x86_64 Error: 1: Operation not permitted Disconnected
Please help me to resolve the issue.
Thanks,
Nishitha

Hi Ratnajit,
I am too facing the same error but my ORACLE is not starting,
Here are my results of following command:
cat /etc/sysctl.conf
# created by /sapmnt/pss-linux/scripts/sysctl.pl on Wed Oct 23 22:55:01 CEST 2013
fs.inotify.max_user_watches = 65536
kernel.randomize_va_space = 0
##kernel.sem = 1250 256000 100 8192
kernel.sysrq = 1
net.ipv4.conf.all.promote_secondaries = 1
net.ipv4.conf.all.rp_filter = 0
net.ipv4.conf.default.promote_secondaries = 1
net.ipv4.icmp_echo_ignore_broadcasts = 1
net.ipv4.neigh.default.gc_thresh1 = 256
net.ipv4.neigh.default.gc_thresh2 = 1024
net.ipv4.neigh.default.gc_thresh3 = 4096
net.ipv6.neigh.default.gc_thresh1 = 256
net.ipv6.neigh.default.gc_thresh2 = 1024
net.ipv6.neigh.default.gc_thresh3 = 4096
vm.max_map_count = 2000000
# Modified for SAP on 2013-10-24 07:14:17 UTC
#kernel.shmall = 2097152
kernel.shmall = 16515072
# Modified for SAP on 2013-10-24 07:14:17 UTC
#kernel.shmmax = 2147483648
kernel.shmmax = 67645734912
kernel.shmmni = 4096
# semaphores: semmsl, semmns, semopm, semmni
kernel.sem = 250 32000 100 128
fs.file-max = 65536
net.ipv4.ip_local_port_range = 1024 65000
net.core.rmem_default = 262144
net.core.rmem_max = 262144
net.core.wmem_default = 262144
net.core.wmem_max = 262144
And here is mine Limit.conf File
cat /etc/security/limits.conf
#<domain>      <type> <item>         <value>
#*               soft    core            0
#*               hard    rss             10000
#@student        hard    nproc           20
#@faculty        soft    nproc           20
#@faculty        hard    nproc           50
#ftp             hard    nproc           0
#@student        -       maxlogins       4
# Added for SAP on 2012-03-14 10:38:15 UTC
#@sapsys          soft    nofile          32800
#@sapsys          hard    nofile          32800
#@sdba            soft    nofile          32800
#@sdba            hard    nofile          32800
#@dba             soft    nofile          32800
#@dba             hard    nofile          32800
# End of file
# Added for SAP on 2013-10-24
#               soft    nproc   2047
#               hard    nproc   16384
#               soft    nofile 1024
#               hard    nofile 65536
@sapsys                 soft   nofile          131072
@sapsys                 hard   nofile         131072
@sdba                  soft nproc          131072
@sdba                  hard   nproc         131072
@dba                 soft    core           unlimited
@dba                 hard     core          unlimited
                  soft     memlock       50000000
                  hard     memlock       50000000
Here is mine   cat /proc/meminfo
MemTotal:       33015980 kB
MemFree:        29890028 kB
Buffers:           82588 kB
Cached:          1451480 kB
SwapCached:            0 kB
Active:          1920304 kB
Inactive:         749188 kB
Active(anon):    1136212 kB
Inactive(anon):    39128 kB
Active(file):     784092 kB
Inactive(file):   710060 kB
Unevictable:           0 kB
Mlocked:               0 kB
SwapTotal:      33553404 kB
SwapFree:       33553404 kB
Dirty:              1888 kB
Writeback:             0 kB
AnonPages:       1135436 kB
Mapped:           161144 kB
Shmem:             39928 kB
Slab:              84096 kB
SReclaimable:      44400 kB
SUnreclaim:        39696 kB
KernelStack:        2840 kB
PageTables:        10544 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:    50061392 kB
Committed_AS:    1364300 kB
VmallocTotal:   34359738367 kB
VmallocUsed:      342156 kB
VmallocChunk:   34359386308 kB
HardwareCorrupted:     0 kB
AnonHugePages:    622592 kB
HugePages_Total:       0
HugePages_Free:        0
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:       2048 kB
DirectMap4k:       67584 kB
DirectMap2M:    33486848 kB
Please let me know where i am going wrong.
Wat thing basically u check on /proc/meminfo command
Regards,
Dipak

ARD: Unable to get shared memory

Hi,
Has anyone encountered this problem with ARD 3.
As I try to open it it doesn't start and gives me get the following error message.
"The Remote Desktop Administrator software failed to start due to an unexpected error. The Remote Desktop software may not be correctly installed or the computer may require a restart"
Rebooting the server is no help.
ARD has worked flawlessly for 2yrs untill now.
When I check the console the lonly thing related to ARD there says:
"ARD: Unable to get shared memory"
Any suggestions?
//Carlos

It sounds like you have in incompatiblity between the version of the ARDAgent client software and the Remote Desktop Admin application on your admin machine. You should check the versions on both and make sure they are the same.

ORA-27123 unable to attach shared memory segment

Running oracle 8.1.5.0.0 on Redhat 6.0 with kernel 2.2.12, I keep getting the error ORA-27123 unable to attach shared memory segment when trying to startup and instance with an SGA > 150 MB or so. I have modified the shmmax and shmall kernel parameters via the /proc/sys interface. The relevant output of ipcs -l is below:
------ Shared Memory Limits --------
max number of segments = 128
max seg size (kbytes) = 976562
max total shared memory (kbytes) = 16777216
min seg size (bytes) = 1
This system has 2gb of physical memory and is doing nothing except oracle.
I changed the shmmax and shmall parameters after the instance was created, was their something I needed to do to inform Oracle of the changes?

High JW,
i had the same problem on my installation.
The solution is written in the Oracle8i Administrator Refernece on page 1-26 "Relocating the SGA"
a) determine the valid adress range for Shared Memory with:
$ tstshm
in the output Lowest & Highest SHM indicate the valid adress range
b) run genksms to generate the file ksms.s
$ cd $ORACLE_HOME/rdbms/lib
$ $ORACLE_HOME/bin/genksms -b "sga_beginn_adress" > ksms.s
c) shut down any instance
d) rebuilt the oracle exe in $ORACLE_HOME/rdbms/lib
$ make -f ins_rdbms.mk ksms.o
$ make -f ins_rdbms.mk ioracle
the result is a new oracle kernel that loads the SGA at the adress specified in "sga_beginn_adress".
regards
Gerhard

ORA-04031: unable to allocate 64 bytes of shared memory

Hi All,
We are performing System copy on a distributed environment with OS Windows 2003 and DB Oracle 10.2.0.4
While importing the Database (ABAP) only ,we are facing error and 5 import steps are failing in Import ABAP phase.
Error is "ORA-00604: error occurred at recursive SQL level 1
ORA-04031: unable to allocate 4120 bytes of shared memory ("shared pool","select user#,type# from user...","Typecheck","kgghteInit")
(DB) INFO: disconnected from DB"
There is already one Oracel Instance OracleXX1 is runing this is the second instance and the server has around 1.75 GB RAM...i
Can you please suggest what could be the error.
Regards
Ajay

Dears,
Please try increase your database parameter shared_pool_size in pfile and then try to resume the activity.
Regards,
Shivam

ORA-04031: unable to allocate 4096 bytes if shared memory

Hello Gurus,
Did anyone got this type of error before:
ERROR:
ORA-20414: Materialized View refresh failed - ORA-12008: error in materialized view refresh path
ORA-04031: unable to allocate 4096 bytes of shared memory ("shared pool","IDX_MIF_SITE","pacdHds_kkpaco","stP_kkpacd: kkpodPacdInit")
Every sunday full refresh of the data warehouse is scheduled. This sunday it didn't complete and gave us the above error. This can be solved by increasing the shared pool memory size. But DBA doesnot want to increase it every sunday(This has been going on for 3 weeks now) and it's not feasible to increase like this everytime.
We want to find the actual cause of it and fix?
Does anyone know the solution or can throw some light on this issue?
Thanks,
Sanjay

We want to find the actual cause of it and fix?The cause is simple - you have run out of memory assigned to the Shared Pool in the SGA.
The root cause is more of an issue. The Shared Pool is mostly used for keeping the SQL statements and supporting information (such as cursor support). Each unique SQL statement requires it's own area in the shared pool, however identical statements can used the same (shared) area. Shared Pool is also used to store the 'current' data dictionary (table, view, etc.) information. And in some cases, it's also used for 'large' operations such as direct path insert block builds.
Some of the possible reasons for running out of shared pool might include
- it's simply undersized;
- not enough SQL is actually shareable;
- the large pool has not been allocated.
That second one is frequent when the application builds up SQL statements by concatenating pieces, including literals (user input) and then executing the unique statement. This is a common technique by developers using .Net, Perl or having SQL Server background. (That mode of operation is very susceptible to SQL Injection.)
You can get a lot more info from:
- searching the forum;
- looking in the docco (Concepts manual and Performance Tuning guide);
- books, like Tom Kyte's "Expert One on One Oracle", "Effective Oracle By Design", and newer on apress.com

What should be started and enabled in SQL express 2008 R2? Shared memory, TCP/IP , named pipes, VIA

I copied my Visual Studio 2008 projects to a new computer and am having trouble getting the database to attach to my website to continue with it.
I uninstalled SQL 2005 express and installed SQL 2008 R2 Express.
When I looked in the SQL Server configuration manager, I wasn't sure what should be running and what should be stopped and what protocols should be enabled, etc so I started everything and enabled everything.
However, the SQL Server Agent will not start. Maybe I did something wrong by enabling everything. I have everything to start automatically, and all enabled:
SQL Native Client: I right clicked and opened and under client protocols, have enabled all: Shared memory, TCP/IP , named pipes, VIA
and under SQL Server Network Configuration, I opened that and under there is listed protocols for SQLEXPRESS AND I enabled same things: Shared memory, TCP/IP , named pipes, VIA
When I could not start the SQL Server Agent before from the SQL Server configuration mgr. I went into services and started it that way and it did start. But since I have rebooted, it will not start that way either and I now get this message: Windows could
not start the SQL Server Agent(SQLEXPRESS) Service on local computer. Error 1067
I'm just trying to get my visual studio project working again. Would appreciate any help. Maybe I should uninstall SQL and reinstall 2005??

Windows could not start the SQL Server Agent(SQLEXPRESS) Service on local computer.
As the others already wrote, with SQL Server Express in Version 2008 the "SQL Server Agent" will be installed, but it's not a Feature of the Express Edition and therefore you can't start & use it.
In SQL Server 2005 Express the Agent was completly missing (not installed), therefore you haven't this "issue" before.
Olaf Helper
[ Blog] [ Xing] [ MVP]

Unable to start/stop Personal Web Sharing

I do some web development, so I tried making the necessary changes to run PHP files via localhost. I followed various online articles by making some changes to the httpd.conf file, and then downloading MySQL and a later version of PHP (5.0). Since installing yesterday afternoon, I've been unable to start or stop Personal Web Sharing. Any ideas?
Thank you.
Nathan

Are you sure you got the proper version of each for your platform? Depending on which version you dowloaded it may not have been a universal bianary and you might be running ppc instead of x86 or vice versa. I wouldnt expect you to have broken apache if you made only the modifications you noted in your inital post - but perhaps if it was trying to load the php module and it was the worng platform it might through that error and prevent it fromt starting.. but normally whn php fails it jsut throws a warning and continues without it loaded (at least with Marc's automatic configuration). But thats the only thing i can think of.
So next steps:
1.) Verify you are running the x86/PPC (or Universal) versions of PHP and MySQL (MySQL shouldnt really matter but since its one of the majorchanges before apache broke we'll look at it as well).
2.) on the command line run this command and post the output back here:
<pre style="scrolling: auto; width: 90%;">httpd -V</pre>
3.) lets restore your old config:
<pre style="scrolling: auto; width: 90%;">
sudo cp /etc/httpd/httpd.conf /etc/httpd/httpd.conf.121906.bak
sudo cp /etc/httpd/httpd.conf.default /etc/httpd/httpd.conf
sudo apachectl start</pre>
And then post the ouput of the start command back here.

ORA-04031: unable to allocate 33568 bytes of shared memory in Oracle 10g

Hi,
I am getting following message frequently while taking export in Oracle 10g database:-
EXP-00008: ORACLE error 4031 encountered
ORA-04031: unable to allocate 33568 bytes of shared memory ("shared pool","DBMS_REPCAT_UTL","PL/SQL MPCODE","BAMIMA: Bam Buffer")
ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_REPCAT_UTL"
ORA-06512: at "SYS.DBMS_REPCAT_EXP", line 87
ORA-06512: at line 1
EXP-00083: The previous problem occurred when calling SYS.DBMS_REPCAT_EXP.schema_info_exp
EXP-00008: ORACLE error 4031 encountered
ORA-04031: unable to allocate 16416 bytes of shared memory ("shared pool","SELECT SYNNAM, SYNNAM, SYNTA...","kgghtInit","kgghtInit")
EXP-00000: Export terminated unsuccessfully
Whats could be the reason?

There could be a few reasons causing the problem. From literal message it would look like your shared pool size is small and you need to increase. But the root cause of the problem is a little more complicated than that. I suggest you read metalink doc
Diagnosing and Resolving Error ORA-04031
Doc ID: Note:146599.1

ORA-04301:Unable to allocate 8144 bytes of shared memory

I am using 64 bit version of oracle 10g Release 2 (10.2.0.1.0)
I am randomly getting this error. The full error message is below:
ORA-04301:Unable to allocate 8144 bytes of shared memory("large pool","COMPANYHISTORY","kxs-heap-w","qesaQBinit:buffer")
The table name keeps changing as the queries change. Similarly sometimes instead of "large pool" I get "shared pool" in the above message.
I tried increasing the shared pool size but the problem did not resolve.
Please help
Regards
Madhup

I have already tried that, but I am not able to solve the problem. Is there a way to compute how much space you should define for the shared pool, the large pool etc.
Regards
Madhup

ORA-29855 - Unable to allocate shared memory

Hi,
We are encountering troubles (unable to allocate shared memory) while indexes creation. We tried to increase the share_size_memory (actually 52 mb) but this had no effect on this error. The Oracle error code is ORA-29855.
The database is version 8.1.7, hosted on a Linux machine (RedHat 7.2) with 512 mb of memory. The code used for the index creation works fine on other machines (code from 9iAS Wireless installation) running with Windows 2000 as operation system.
Any help or comment will be appreciated.
Thanks,
Fabrice Clari.
The error message is:
java.sql.SQLException: ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-13200: internal error [ROWID:AAAGDwAAFAAAAvjAAA] in spatial indexing.
ORA-13206: internal error [] while creating the spatial index
ORA-13011: value is out of range
ORA-00600: internal error code, arguments: [kope2ucoll700], [], [], [], [], [], [], []
ORA-04031: unable to allocate 16396 bytes of shared memory ("large pool","unknown object","koh-kghu sessi","kolcalm coll")
ORA-06512: at "MDSYS.SDO_INDEX_METHOD", line 8
ORA-06512: at line 1

Which portion of shared memory did you increase? The error indicates you need to increase large_pool_size. It seems you may also have other problems since you have several errors, and this only relates to the ORA-04031 error.

Centos 5.2 'shared memory init failed' issue - doesn't start

I am running centos 5.2 32bit and I installed FMS 3.0.2 (Tried FMS 3.0.4 also)
FMS installed just fine with the -platformWarnOnly flag.
My problem is it will not start at all, nothing starts. no logs in the /opt/adobe/fms either, I only get logs in /var/log/messages with the following
Apr 8 17:14:48 vid Server[22463]: Process (22463) : shared memory (__FCS__serverstats_) init failed.
Apr 8 17:14:53 vid Server[22475]: Process (22475) : shared memory (__FCS__serverstats_) init failed.
Apr 8 17:21:15 vid Server[22733]: Process (22733) : shared memory (__FCS__serverstats_) init failed.
Apr 8 17:21:20 vid Server[22745]: Process (22745) : shared memory (__FCS__serverstats_) init failed.
I also did a ldd on fmsmaster and symlinked "libasneu.so.1 => not found" to the real file, that did nothing.
Here are some of the rpms that im pretty sure are needed.
[root@vid fms]# rpm -qa | grep compat
compat-gcc-34-g77-3.4.6-4
compat-libgcc-296-2.96-138
compat-glibc-headers-2.3.4-2.26
compat-gcc-34-3.4.6-4
compat-libf2c-34-3.4.6-4
compat-gcc-34-c++-3.4.6-4
compat-libstdc++-296-2.96-138
compat-glibc-2.3.4-2.26
compat-libstdc++-33-3.2.3-61
[root@vid fms]# rpm -qa | grep stdc
compat-libstdc++-296-2.96-138
libstdc++-4.1.2-44.el5
compat-libstdc++-33-3.2.3-61
libstdc++-devel-4.1.2-44.el5
[root@vid9 fms]# rpm -qa | grep nspr
nspr-devel-4.7.3-2.el5
nspr-4.7.3-2.el5
Would appreciate any help guys!!
I also googled my error and there is one post with no answer here: http://forums.adobe.com/message/105674#105674
Thanks!

tmp/ is (/opt/adobe/fms/tmp) 777 and owned by root, I even tried chown'ing to the user that runs fms, no luck.
tmp gets created when i run it the FIRST time:
[root@vid10 fms]# ls -al tmp/
total 8
drwxrwxrwx 2 admin admin 4096 Apr 8 21:15 .
drwxr-xr-x 11 admin admin 4096 Apr 8 21:09 ..
-rwxrwxrwx 1 admin admin 0 Apr 8 21:09 __FCS__serverstats__shm_mem
-rwxrwxrwx 1 admin admin 0 Apr 8 21:09 __FCS__serverstats__shm_mtx
Could it be something with the shm setting, maybe sysctl?
I have 4GB of ram in this machine. Same exact machine works perfect on rhel 4
I appreciate your quick reply.

Unable to start DSC Shared Memory

Similar Messages

Maybe you are looking for