Only a check... Did you use ant fress_install or ant fresh_install?. You can check the database connection with dspace command at your bin directory: dspace test-database.
Here is an output valid: C:\dspace\bin>dspace test-database Using DSpace installation in: C:\dspace Attempting to connect to database: - URL: jdbc:postgresql://localhost:5432/dspace - Driver: org.postgresql.Driver - Username: zzzyyyy - Password: xcxcvxcv - Schema: null Testing connection... Connected successfully! If doesn't work, check your firewall into server, unblock the port 5432 (postgres default) and check de jdbc string connection in dspace.cfg to match with your configuration. Another issue would be that you haven't allow Postgres connections from your server in the pg_hba.config in Postgres server. If in Postgres configuration you haven't declared as allowed the server that make the query, you will have an error. Our instalation use Windows, Tomcat and Postgres. Dennis Tobar El 29/11/2011 01:30, "shiva kumara" <[email protected]> escribió: > > Dear Helix84, > > > Thank you so much for your valuable reply. > > > I agree with you, But one more clarification is that I neither upgrade my > postgresql database nor used ant fress_install or ant update command. The > problem was that our windows shows the message that “this is not genuine > versions”. I called system admin people and told them to make it genuine > versions. Then he did the some patches to windows. Now I can’t see dspace > database, only Postgresql 9.0 database can be seen in the database list. > > > > If the database is really empty, I do not have any backup of the dspace > collection. So what is the procedure to initiate and integrate the new > database with existing dspace. > > > Kindly assist me to solve this problem. > > Thanks a ton, > > -- > Regards > Shivakumara RM > http://sites.google.com/site/aigslibrary > https://sites.google.com/site/shivakumararm/ > > >> >> This error just means that DSpace cannot connect to the database, it >> doesn't say that the database is empty. This is most likely because >> you forgot to set database information in dspace. During the upgrade, >> you probably didn't fill in configuration options of your >> institutution in the new dspace.cfg in >> [dspace-src]/dspace/config/dspace.cfg which gets copied to >> [dspace]/config/dspace.cfg. You can still find a backup of the old >> dspace.cfg in [dspace]/config-[date_of_upgrade]/dspace.cfg. Please, >> follow the manual when doing upgrades, this wouldn't happen. >> >> If the database is really empty, you'll have to restore it from >> backup. This could have happened if you used ant fresh_install instead >> of ant update when upgrading. Again, please follow the manual closely. >> >> Regards, >> ~~helix84 > > > > > > > > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > DSpace-tech mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/dspace-tech > ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
