Issue while setting up ReportServer for first time.

Rishabh · July 1, 2016, 6:22pm

Getting below error while setting up report server for first time.
i am using 3.0.2, oracle dB and tomcat 8.
it’s able to setup connection but could not able to Validate schema.

DB Config

hibernate.dialect: net.datenwerke.rs.utils.hibernate.Oracle10gDialect (OK)
hibernate.connection.driver_class: oracle.jdbc.driver.OracleDriver (OK)
hibernate.connection.url: jdbc:oracle:thin:@stomcqadb4.va.neustar.com:2115:omsds
dev (OK)
hibernate.connection.username: report_server
hibernate.connection.password: *******
hibernate.default_schema: omsdsdev

Connection Test: OK
Schema Version: RS3.0-8

14:19:01.779 INFO n.datenwerke.rs.EnvironmentValidator - Validating database sc
hema…
14:19:06.890 ERROR n.datenwerke.rs.EnvironmentValidator - Schema-validation: mis
sing table [RS_ACE]
14:19:06.893 ERROR n.d.rs.ReportServerServiceConfig - ReportServer encountered a
n error while validating its environment. Startup interrupted.

Thomas_Davies · July 2, 2016, 9:19am

Hello,

and welcome to the ReportServer forum.

Did you run the DDL script to set up the ReportServer tables? The DDL scripts are located in the ddl directory.

Best Regards,
Thomas

Rishabh · July 3, 2016, 2:10pm

Yes, I have run those ddl queries and am seeing tableRS_ACE table is there as well.

Guest · July 4, 2016, 10:03am

Hi,

could your default_schema value be wrong? In most cases this either is not needed at all, or is the same as your user name.
If this is correct, make sure the user report_server really has access to the omsdsdev schema/user.

Cheers,
Thorsten

Rishabh · July 4, 2016, 2:26pm

Somehow, I am able to see below output in logs:

Connection Test: OK
Schema Version: RS3.0-8
04-Jul-2016 19:24:02.715 INFO [localhost-startStop-1] net.datenwerke.rs.EnvironmentValidator.startup Validating database schema…

But, After above logs, The server seems to be taking huge time (Around 25 minutes) to startup. Why is tomcat taking so much time in validating schema?

Thomas_Davies · July 4, 2016, 6:11pm

The schema validation shouldn’t take more than a few seconds. Is your database behind a high latency link, like for example some kind of vpn? If so you should probably reconsider your setup and try to get the database and the application server closer to each other.

You can also try disabling the schema validation in the persistence.properties file by setting rs.validateschema=false but very likely everything else will be just as slow.

Cheers,
Thomas

Rishabh · July 5, 2016, 12:47am

Thanks Thorsten!
Much appreciated

Don’t know what was the issue earlier but when I changed default_schema to my username (report_server), it worked for me.

@Thomas: Since I was on VPN and there was some issue in network connectivity that’s why it took so long. Now able to run the report server and exploring various options on it.

Thanks to all!! Highly appreciated

Thanks
Rishabh