SUMMARY - SQL Error messages
Posted in 1993
Topics: Installation, Setup & Upgrades, Storage & Space Management, Error Codes & Troubleshooting, Connectivity: ESQL/C, 4GL & Embedded SQL
Problem solved. There were two issues I ignored. First, the problem involved both ISQL and 4GL and all users were affected. Second, all the permissions were OK, and all user environment variables were set properly, or were corrected during my tests. The resolution was to re-install the engine, but not to initialize the dbspace. I should have bitten the bullet and done this after my re-install of ISQL. This cleared up the problem, but does not clarify why Informix lost its mind during the installation of the I-STAR product. I have not used I-STAR before, but I have installed On-Line many times on many platforms. Enough defensive comments, I should be happy to learn something new today. :) I will try a re-install tomorrow morning (early enough to re-install On-Line!) and see if this 'takes'. Thanks for the quick response from the mailing list: Hal Wigoda Jack Parker Bob Baskett -peb } OK, I give up. I have administered Informix engines far and wide, and } yet I am faced with a rather simple problem but the solution eludes } me. Maybe the list can help. } } If you can send mail to me at peb@scdipc0.ueci.com, I would appreciate and } will summarize to the list. Thanks in advance. } } ----- } } I installed the I-STAR product onto our development machine (Sun IPC). } Just after I finish the install, one of the programmers is getting error } messages from the engine. } } I checked all permissions, including the dbspace device permissions, and } they look fine. All environment variables are defined and appear to be } fine. The engine appears to be running fine. } } I re-installed ISQL, but no joy. I would like to avoid re-installing the } engine which would require a restore of the development database. } } Compiling 4GL code, you receive the message: } } GLOBALS } | } | Not owner } | See error number -1. } | } | The database "tracsy" cannot be found or opened. If the database } | exists, check the database permissions on the database. In } | addition, check the system permissions on the database directory } | and its ascendant directories. } | See error number -4305. } } Running ISQL you get: } } 1: Not owner } 123: ISAM error: no shared memory -- Paul Begley Internet: peb@scdipc0.ueci.com Raytheon Engineers & Constructors Voice: 215-422-3997 Philadelphia, PA FAX: 215-422-3800