E_VW1035 Cannot connect to Vectorwise server - ingres

I started with vectorwise, i try to create database but i can do this.
ingres#xx:~$ createdb essai
I have an error :
Creating database 'essai'. . .
E_VW1035 Cannot connect to Vectorwise server.
(Mon Jun 17 09:01:01 2013)
Creation of database 'essai' abnormally terminated.
So how i can resolve this error ? and how i can drop database ? because when i retry
ingres#xx:~$ createdb essai
I see essai exist already
Creating database 'essai'. . .
E_DU3021_DB_EXISTS_CR
The database, essai, already exists.
Creation of database 'essai' abnormally terminated.

The documentation for Vectorwise is available at docu.actian.com
Here you will find references to all of the commands you can use.
To answer the second question first. If you know you can destroy the database then :
destroydb dbname
will do this for you.
If this is a new installation of Vectorwise - try looking in the vectorwise.log file in $II_SYSTEM/ingres/files ( or on Windows down the C:\ProgramData\Actian path ).
You will find an error condition here. In this case if you server is under configured this will be due to insufficient resources - most likely RAM.
If this is the case then you will need to either add more physical RAM to this server (4GB is the minimum recommended) or update the vecvtorwise .conf file to reduce the memory requirements (this would be for a dev/test ONLY solution!)
If this is not your problem - please post the error you see.
If it is the solution you need please update this post.

Related

Postgresql and ssl start up error

I am new to freenode and postgresql. I am trying to migrate from mysql to postgresql. Currently trying to set up server for ssl. Have created my server certs and configured the .conf files for ssl according to the manual as far as I can see. Trying to restart postgre sql service fails. Windows event log gives me an event ID of 0 and says
pg_ctrl could not start server examine the log output.
I can't find any log detailing the failure to start in the postgresql folders.
I have tried to register the pgevent.dll as advised by the postgresql manual (18.11 of most recent version), but I get an error message
The module "C:postgreSQL\pg10\lib\postgresql\pgevent.dll" was loaded but the entry-point DllRegisterServer was not found
I believe that means it is either not a registrable dll or it's corrupt.
Can anyone please advise how I can track on Windows the error that is causing Postgre to fail to start?

Firebird error: cannot start transaction for password database

I am looking for some help - today my firebird database has stopped opening the database files with the following error:
engine code: 335544654
engine message: cannot start transaction for password database
I've tried googling but can't find any resources that have any relevant information.
Thanks
I eventually got this resolved by doing a number of restores of the security2.fdb database.
In my case, there was not enough data space in /var.
I cleared the contents of "/var/spool/clientmqueue/".

Postgresql query did not terminate, after restart the service postgresql doesn't start

At my work I was running a complex query. I cancelled it and went home yesterday. This morning in the back the query was impossible to be terminated, also with the 'terminate backend' functionality. A colleague of mine restarted the host machine where postgres is installed. After the machine restart, the postgres database sever would not start up.
In my log files I see the error:
'pg_ctl: this data directory appears to be running a pre-existing postmaster'
I am not sure how to handle this problem. I could try to fix it or try to extrapolate the data from the save files. What is the most logical step to take and do you know how to fix this?
Earlier it gave this error message :
2016-01-28 15:52:33 GMT FATAL: lock file "postmaster.pid" already exists
2016-01-28 15:52:33 GMT HINT: Is another postmaster (PID 2100) running in data directory "C:/PostgreSQL/9.1/data"?
UPDATE... I located the file postmaster.pid and deleted it. Now I am restarting the computer and hoping it will start.
UPDATE... It works now. I rebooted the computer and postgres just instantly started. Happy as a child but at the same time not fully satisfied because of the following forum: https://superuser.com/questions/553045/fatal-lock-file-postmaster-pid-already-exists . Here it is stated to NEVER delete the postmaster.pid because of possible data corruption. So because of that I will backup all databases I have in postgres now.
So if anyone can share some more light on my ICT adventure of today I would be very satisfied. That is why I will not state that this question is answered, since I have no idea what went wrong and perhaps will run into it again someday.
The explanation is pretty straightforward. PostgreSQL writes the process ID to a file called postmaster.pid — the presence of the file is supposed to indicate that the server is running. When the PostgreSQL shuts down cleanly, it removes the postmaster.pid file.
However, when your colleague restarted the host machine, the PostgreSQL server got killed without having had a chance to remove the postmaster.pid file. Therefore, when you tried to start PostgreSQL, the presence of the file made it look complain that the server was already running.
This answer provides more complete advice. In general, you should never delete postmaster.pid for no good reason, because it's supposed to help prevent two servers from running at once on the same data files. However, if you are certain that the process indicated by the postmaster.pid file is already dead, then by all means just delete the stale PID file manually.
In windows Delete all running postgres processes and start the service

Replic-Action log error Cannot open Link: TNS Could not resolve the service name

Hi I am working with ReplicAction tool to transfer data from Lotus Notes View to Oracle Database.
When i Create the link document for Oracle DB it is created successfully without any error
When I create the Include Table for Oracle Db it is created successfully and all columns are listed
When i create the Replication it is also created successfully,
But when the job executes it gives the error is log :
05/08/2012 01:37:16 AM Starting Replication: BADtoProductPortal
05/08/2012 01:37:19 AM Error: <ODBC Error> [DataDirect][ODBC Oracle driver][Oracle]ORA-12154: TNS:could not resolve service name
05/08/2012 01:37:19 AM Error: Information: Unable to open Link: PPLink
05/08/2012 01:37:19 AM Error: Replication to Link <PPLink> did not complete
05/08/2012 01:37:20 AM End of Replication: BADtoProductPortal
If the error is with service name, Then i think we should not be able to create Link document also.
When i use ODBC connection for link, then i am unable to create Replication job, giving the error like Notes Data field "ID" does not match the source data field.
But i know it was working before.
I suggest to check that the TASK runing the job uses the same TNS entry as you are doing "manually".
I suggest to check that the TASK has also access to your Oracle driver. This tasks has right to run it?
ORA-12154 error is thrown during the logon process to a database. This error indicates that the communication software (TNS) in Oracle ( SQL *Net or Net8 ) did not recognize the host/service name specified in the connection parameters.
So the issue is clearly a type en "environment difference" between your configuration when you run manually the replication and when the job run it.
Hope I help
I'm assuming here that when you successfully replicate you're doing it manually from your local machine, and when the job fails it's running scheduled on a server. If that's the case I agree with Emmanuel. Remember running the job locally uses the local tnsnames.ora file, running it scheduled uses the tnsnames.ora file on the server. You may not be aware of anything changing but are you responsible for maintainance on the server?

How recover sybase database (unknown db version)

I have a database file (*.db) that need to be recovered.
The bad is, the end-user have null idea of the version of the database. Not know the password. The original developer is lost. The computer where was installed was formatted. We have not experience in this database software. Yeah, nightmare.
My guess is a old database. I'm trying to open it in Sybase 11, dev edition.
I follow this steps: http://dcx.sybase.com/1101en/sachanges_en11/unloading-reloading-upgrading-newjasper.html
I try to use the UNLOAD utility from command line & from the Sybase central utility. From command line I do:
./dbinfo -c "DBF=/Users/mamcx/Downloads/CEMDE_ENDOCRINO_S.A.DB;UID=DBA;PWD=sql"
SQL Anywhere Information Utility Version 11.0.1.2045
Unable to start specified database: '/Users/mamcx/Downloads/CEMDE_ENDOCRINO_S.A.DB' was created by a different version of the software
Ok, I try to unload:
./dbunload -c "DBF=/Users/mamcx/Downloads/CEMDE_ENDOCRINO_S.A.DB;UID=DBA;PWD=sql" -n /Users/mamcx/Desktop/
SQL Anywhere Unload Utility Version 11.0.1.2045
Connecting and initializing
***** SQL error: Unable to start database server
Ok, from the server admin tool:
dbunload -v -c "UID=dba;PWD=***;DBF=/Users/mamcx/Downloads/CEMDE_ENDOCRINO_S.A.DB" -an "/Users/mamcx/Desktop/baba.db" -ap 4096 -ea None -ii -sa -so _sc866192545
Connecting and initializing
***** SQL error: Unable to start database server
An error occurred while attempting to unload the database '/Users/mamcx/Downloads/CEMDE_ENDOCRINO_S.A.DB'.
Exist a way to know the version of the database server used to create this? Is possible to recover this file?
I don't know how to get the version out of the Database File if you are not able to start it.
You could get a hint from the hopefully existing Client PC's. Check the ODBC Driver Version they have installed.
I had good success with the support of Sybase. If you or your client has a support contract you can get them involved.
HTH
Try to simply start a server with that database and capture the output with -z -o server.out. The server.out file should contain a more specific error telling you why it can't start the database. This error can occur if you are trying to start something that is not a SQL Anywhere database.
You may also want to post this question over at http://sqlanywhere-forum.sap.com/.