Sponsored Content
Top Forums UNIX for Advanced & Expert Users PCC-F-NOERRFILE, unable to open error message file, facility PR2 Post 66203 by jim mcnamara on Friday 11th of March 2005 12:59:58 PM
Old 03-11-2005
enter the command:

proc

You should see that Pro*C can find its default config file:
/dsw/app/oracle/product/920/precomp/admin/pcscfg.cfg

The "/dsw/app/oracle/product/920" maybe different on your system, but it is $ORACLE_HOME.

The error you are getting indicates that Pro*C cannot find component files, specifically it tried to give you an error message and could not find the error text file.
 

10 More Discussions You Might Find Interesting

1. Programming

PCC-s-02201 error

While compiling and executing i get the following error. Error at line 1200, column 1 in file xxx.pc { 1 PCC-S-02201,Encountered the symbol "{" when expecting one of the following: ; , = < [ please help (1 Reply)
Discussion started by: musavir19
1 Replies

2. UNIX for Dummies Questions & Answers

Open a file in VI and I get the message below:

@ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ (6 Replies)
Discussion started by: bobo
6 Replies

3. Solaris

Error Message: find: cannot open /: Stale NFS file handle

I am using the "find" command below and it respond with the error message " find: cannot open /: Stale NFS file handle" what does it mean? what can I do about it? Need advice, thanks. below are the command that I enter, the respond and the error message: root@ScripServer:/# find / -name... (1 Reply)
Discussion started by: ezsurf
1 Replies

4. Shell Programming and Scripting

PCC-F-NOERRFILE, unable to open error message file

Hi, I was compiling few C programs in the unix server and getting the following error message rm: /home/a0xxx28/AVT/SEEDLIBRARYDB/LIB/*.a non-existent proc MODE=ANSI CODE=ANSI_C INCLUDE=/home/a0xxx28/PVT/SEEDLIBRARYDB/INCLUDE INCLUDE=/home/a0xxx28/PVT/SEEDLIBRARY/INCLUDE ... (1 Reply)
Discussion started by: kavithakuttyk
1 Replies

5. UNIX for Dummies Questions & Answers

Unable to use the CDE Facility

Hello I have a SunBlade 1000 workstation and I cannot login via CDE. All I get is a console login prompt. I then have to login via root and I just get the command line interface. I have being doing some research on the UNIX forum and the problem may lie with the content in etc/hosts file.... (7 Replies)
Discussion started by: tjwops
7 Replies

6. UNIX for Dummies Questions & Answers

error message when use fork with open file

I get this message when I write myshell.c program "VM pagefault:SIGSEGV bad add 0x0 err 0x4 nopage read myshell PM: ciredump signal 11 for 1725 /myshell memory fault (core dumped)" /* RCS information: $Id: myshell.c,v 1.2 2006/04/05 22:46:33 elm Exp $ */ #include <stdio.h> #include <unistd.h>... (1 Reply)
Discussion started by: rosecomp
1 Replies

7. Solaris

Can't open boot_archive error message

Hello guys, Thanks for all your precious tips. I hope you can give me some advice again. This time I am having an issue with a SUN FIRE V240 (SOLARIS 10). The server doesn't boot, normally , first we had a file system error ====================+FIRST ERROR... (6 Replies)
Discussion started by: feg
6 Replies

8. Shell Programming and Scripting

Unable to open a file in perl

Not able to open a file using this code why not? use strict; use warnings; my $file = "verInfo.txt"; unless(open FILE, $file) { # Die with error message # if we can't open it. die "\nUnable to open $file\n"; } my $line = <FILE>; print $line; close FILE; (7 Replies)
Discussion started by: srijith
7 Replies

9. UNIX for Dummies Questions & Answers

xWindows error: xhost unable to open display

I am trying to direct a AIX display to my XWindows and I am at a dead end now! So this what I've done so far: 1. In putty settings, I set "Enable X11 forwarding" and also set "X diplay location" to "localhost:0" (without quotes, of course) 2. Via putty, connected to my AIX server 3. On... (1 Reply)
Discussion started by: shoefiend
1 Replies

10. Shell Programming and Scripting

When trying to open file Message:-Terminal too wide?

Hi, I am trying to open small size file only in vi editor on solaris or Linux machine but it giving message "Terminal too wide" and then I have to come out. As shown below:- -rwxr-x--- 1 rkycadm rkycprd 2445 Sep 12 04:06 $ vi file.txt Terminal too wide :q! ----------... (2 Replies)
Discussion started by: RahulJoshi
2 Replies
qmail-log(5)							File Formats Manual						      qmail-log(5)

NAME
qmail-log - the qmail activity record DESCRIPTION
qmail-send prints a series of lines describing its activities. Each possible line is described below. STATUS
status: local l/L remote r/R ... qmail-send is waiting for l local deliveries and r remote deliveries. The concurrency limits are L and R. status: exiting qmail-send is done. FATAL PROBLEMS
alert: cannot start: ... qmail-send is unable to prepare itself for delivering messages; it is giving up. This normally indicates a serious configuration error, but it can be caused by a temporary lack of resources. alert: oh no! lost ... One of the other daemons has died. qmail-send will exit as soon as possible. SERIOUS PROBLEMS
alert: unable to append to bounce message... qmail-send is unable to record a permanent failure, usually because the disk is full. This is a very serious problem; qmail-send cannot proceed without recording the results. It will try again in ten seconds. alert: out of memory... qmail-send tried to allocate more memory and failed. It will try again in ten seconds. alert: unable to opendir... qmail-send is having trouble reading a file list from disk, usually because the system's file descriptor table is full, but possibly because permissions are set incorrectly. It will try again in ten seconds. alert: unable to switch back... qmail-send was sent SIGHUP, and it is unable to reenter the queue directory. This is a very serious problem; qmail-send cannot pro- ceed outside the queue directory. It will try again in ten seconds. alert: unable to reread... qmail-send was sent SIGHUP, but it is unable to read the new controls. It will continue operating with the original controls. MESSAGES
new msg m qmail-send is going to preprocess a queued message. The message number, m, is its disk inode number. After a message is removed from the queue, its number can be reused immediately. info msg m: bytes b from <s> qp q uid u Message m contains b bytes; its envelope sender is s; it was queued by a user with user ID u. q is a long-term queue identifier, the process ID of the qmail-queue that queued the message. bounce msg m qp q Message m had some delivery failures. The long-term queue identifier of the bounce (or double-bounce) message is q. triple bounce: discarding ... Message m had some delivery failures, but it is already a double-bounce message, so it must be thrown away. Triple-bounce messages do not exist. end msg m qmail-send is about to remove message m from the queue. DELIVERIES
starting delivery d: msg m to ... qmail-send is telling qmail-lspawn or qmail-rspawn to deliver message m to one recipient. The delivery number, d, starts at 1 and increases by 1 for each new delivery. delivery d: success: ... Delivery d was successful. delivery d: failure: ... Delivery d failed permanently. The message will bounce. delivery d: deferral: ... Delivery d failed temporarily. This recipient will be retried later. delivery d: report mangled, will defer There is a serious bug in qmail-lspawn or qmail-rspawn. This recipient will be retried later. WARNINGS
internal error: delivery report out of range qmail-lspawn or qmail-rspawn has supplied a report on a nonexistent delivery. This is a serious bug. qmail-clean unable to clean up ... For some reason qmail-clean is unable to remove the indicated file. It will try again later. trouble fsyncing ... qmail-send was unable to write to disk the results of preprocessing a queued message. It will try again later. trouble in select There is an operating system bug. trouble injecting bounce message... qmail-send was unable to queue a bounce message, usually because the disk is full. It will try again later. trouble marking ... qmail-send was unable to record the result of a successful or permanently unsuccessful delivery. This means that the delivery will be tried again later. trouble opening ... qmail-send was unable to open the list of local or remote recipients for a message. It will try again later. trouble reading ... Either qmail-send is unable to read a recipient list, or it is unable to read the envelope of a queued message, or it is out of mem- ory. Whatever it was doing, it will try again later. trouble writing to ... qmail-send was unable to preprocess a queued message, usually because the disk is full. It will try again later. unable to create ... qmail-send was unable to preprocess a queued message, usually because the disk is out of inodes. It will try again later. unable to open ... qmail-send is unable to read the envelope of a queued message for preprocessing. It will try again later. unable to start qmail-queue... qmail-send is unable to queue a bounce message, usually because the machine is almost out of memory. It will try again later. This can also be caused by incorrect settings of $QMAILQUEUE or errors in a program or script which $QMAILQUEUE points to. unable to stat ... qmail-send is unable to obtain information about a file that should exist. It will try again later. unable to unlink ... qmail-send is unable to remove a file. It will try again later. unable to utime ... qmail-send is about to exit, and it is unable to record on disk the next scheduled delivery time for a message. The message will be retried as soon as qmail-send is restarted. unknown record type in ... There is a serious bug in either qmail-queue or qmail-send. SEE ALSO
qmail-send(8) qmail-log(5)
All times are GMT -4. The time now is 09:49 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy