Sponsored Content
Full Discussion: Prophet 21 acclaim system
Operating Systems AIX Prophet 21 acclaim system Post 302999332 by vbe on Saturday 17th of June 2017 04:03:47 AM
Old 06-17-2017
My first thoughts as I have no idea what is prophet21 acclaim system abut little googling says its an ERP and perhaps you have a progress DB, shm segment this I know better and would suspect is responsible of the second line error

What user is used for prophet/progress db ? And what is the ulimit? But I would say I doubt it be here only this is the first thing to look at... cmd:
Code:
 ulimit -a

and should be unlimited...

What is the size of your shared memory? How much RAM on the system?
when total amount of shared memory a process tries to attach to exceeds the OS-allowed limit, you get such error, on a 32bit OS ( which Im sure is the case...) it would be around 1.6 GB ( that is what I had for oracle instances...)
So next Q: how many instances of progress or ?db do you have running?
Is this the first time?
When was the last time the system was rebooted?
If not after a reboot
I suggest to look if more than one instance running at possible shared memory fragmentation, if you see no solution there, then stop the/all instance of db ( because that message means the following line cannot execute and I understand a db instance cant be brought up... So one stopped see what is left in shared memory, is there any memory still attached to db ? If so it should not and remove it - It may be the culprit
And try to start all again
Of course the easiest would be a reboot that would clean the lot... Maybe the easiest and fastest if you can...

A totally different case if it occured just after a reboot of course, which doesnt mean all the above is absurd, but needs to be figured out in what way it could be affected by the sort:
Any new instance added?
Has someone changed any parameters? ( especially for the instance - (like oracle's SGA...)
If not, anything is the system logs??? errpt -a...

Last edited by vbe; 06-17-2017 at 05:09 AM.. Reason: typos... sorry Im in bed...
 

9 More Discussions You Might Find Interesting

1. Solaris

rsh commands not getting executed from Solaris 10 System to AIX System

Hi Friends, I am trying to execute rsh commands from Solaris 10 system to AIX system. When I give; Solaris10# rsh <hostname> ls -l , it gives me an error rshd : 0826-826 The host name for your address is not known At the same time, Solaris10# rsh <hostname> ---- gives me remote shell of... (25 Replies)
Discussion started by: jumadhiya
25 Replies

2. SCO

file system not getting mounted in read write mode after system power failure

After System power get failed File system is not getting mounted in read- write mode (1 Reply)
Discussion started by: gtkpmbpl
1 Replies

3. Shell Programming and Scripting

how to delete files at booting of system (system startup)

hi all I have a problem how to write a shell script which delete files/folder form directory whenever system boot and copy last updated folder/file in the specified directory.pse help me ASAP. i write a script which copy files in directory.I want when system boot up using script it check whether... (1 Reply)
Discussion started by: shubhig15
1 Replies

4. UNIX for Advanced & Expert Users

how to make a full system backup excluding data and restoring it to a new system

Hi, In order to have a sand box machine that I could use to test some system changes before going to production state, I'd like to duplicate a working system to a virtual one. Ideally, I'd like to manage to do it this way : - Make a full system backup excluding the user file system (this... (7 Replies)
Discussion started by: pagaille
7 Replies

5. Solaris

System hangs (freezes) on system bell/beep

I am running OpenIndiana development version oi_148 32-bit on a seven-year-old Dell Inspiron 8600. Seems to be running fine except for one particular annoyance: It freezes whenever a system bell/beep plays. I have mitigated this by turning the system bell off in gnome-terminal, which I use... (3 Replies)
Discussion started by: DeadBadger
3 Replies

6. HP-UX

how to mount a file system from a solaris server into an hp-ux system

Hi all I wonder if its possible to mount on a hp-ux server a file system that was previously mounted on a solaris 10 server. The LUN is on NetApp stoarge. The problem on hp-ux I cannot do pvcreate on the lun (disk) because contains data. Any help will be appreciated FR (2 Replies)
Discussion started by: fretagi
2 Replies

7. AIX

Accessing files on AIX system from Linux system

I have a following requirement in production system 1 : LINUX User: abcd system 2: AIX (it is hosting a production DB) Requirement user abcd from system 1 should have read access on archive log files created by DB on system 2. The log files are created with permissions 540 by user ora ,... (2 Replies)
Discussion started by: amitnm1106
2 Replies

8. AIX

Cloning a system via mksysb backup from one system and restore to new system

Hello All, I am trying to clone an entire AIX virtual machine to a new virtual machine including all partitions and OS.Can anyone help me on the procedure to follow? I am not really sure on how it can be done.Thanks in advance. Please use CODE tags for sample input, sample output, and for code... (4 Replies)
Discussion started by: gull05
4 Replies

9. UNIX for Beginners Questions & Answers

Migrating jobs from COBOL Mainframe system to UNIX system

In a nutshell requirement is to migrate the system from mainframe environment to UNIX environment (MF cobol would be used I guess). I have not much of idea in this field. I need to do some investigation on following points - - Ease of conversion - Known Data compatibility issue - Issue in... (9 Replies)
Discussion started by: Tjsureboy4me
9 Replies
shmop(2)							System Calls Manual							  shmop(2)

Name
       shmop, shmat, shmdt - shared memory operations

Syntax
       #include <sys/types.h>
       #include <sys/ipc.h>
       #include <sys/shm.h>

       char *shmat (shmid, shmaddr, shmflg)
       int shmid;
       char *shmaddr;
       int shmflg;

       int shmdt (shmaddr)
       char *shmaddr;

Description
       The  system  call attaches the shared memory segment associated with the shared memory identifier specified by shmid to the data segment of
       the calling process.  The segment is attached at the address specified by one of the following criteria:

       If shmaddr is equal to zero, the segment is attached at the first available address as selected by the system.

       If shmaddr is not equal to zero and (shmflg & SHM_RND ) is true, the segment is attached at the address given by (shmaddr- (shmaddr modulus
       SHMLBA )).

       If shmaddr is not equal to zero and (shmflg & SHM_RND ) is false, the segment is attached at the address given by shmaddr.

       The segment is attached for reading if (shmflg & SHM_RDONLY ) is true. Otherwise, it is attached for reading and writing.

       The system call detaches from the calling process's data segment the shared memory segment located at the address specified by shmaddr.

Return Values
       Upon successful completion, the return values are as follows:

       o   The system call returns the data segment start address of the attached shared memory segment.

       o   The system call returns a value of zero (0).

       Otherwise, a value of -1 is returned, and errno is set to indicate the error.

Diagnostics
       The system call fails and not attach the shared memory segment, if any of the following is true:

       [EINVAL]       The shmid is not a valid shared memory identifier.

       [EACCES]       Operation permission is denied to the calling process.  For further information, see

       [ENOMEM]       The available data space is not large enough to accommodate the shared memory segment.

       [EINVAL]       The shmaddr is not equal to zero, and the value of (shmaddr- (shmaddr modulus SHMLBA )) is an illegal address.

       [EINVAL]       The shmaddr is not equal to zero, (shmflg & SHM_RND ) is false, and the value of shmaddr is an illegal address.

       [EMFILE]       The number of shared memory segments attached to the calling process would exceed the system imposed limit.

       The fails and does not detach the shared memory segment if:

       [EINVAL]       The shmaddr is not the data segment start address of a shared memory segment.

See Also
       execve(2), exit(2), fork(2), shmctl(2), shmget(2)

																	  shmop(2)
All times are GMT -4. The time now is 05:06 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy