Service Virtualization

Expand all | Collapse all

Error creating bean with name 'dradisInitBean'

  • 1.  Error creating bean with name 'dradisInitBean'

    Posted Jun 22, 2017 03:53 PM

    We have installed CA DevTest 10.1 software and attempting to connect the Enterprise Dashboard to Oracle 12.1 but we are seeing the following exceptions in the  enterprisedashboard.log when we attempt to start up the Enterprise Dashboard.

     

    2017-06-23 01:15:14,372Z (19:15) [main] INFO  dradis.DradisInitBean          - Database Driver Name: Oracle JDBC driver
    2017-06-23 01:15:14,373Z (19:15) [main] INFO  dradis.DradisInitBean          - Database Driver Version: 12.1.0.2.0
    2017-06-23 01:15:14,847Z (19:15) [main] INFO  com.ca.dradis.db.FlywayDbMigration - Schema Version: 13
    2017-06-23 01:15:15,021Z (19:15) [main] WARN  org.springframework.boot.context.embedded.AnnotationConfigEmbeddedWebApplicationContext - Exception encountered during con
    text initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dradisInitBean': Invocation of
     init method failed; nested exception is org.flywaydb.core.api.FlywayException: Schema "SVTOOL" contains a failed migration to version 13 !
    2017-06-23 01:15:15,062Z (19:15) [main] ERROR org.springframework.boot.SpringApplication - Application startup failed
    org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dradisInitBean': Invocation of init method failed; nested exception is org.flywa
    ydb.core.api.FlywayException: Schema "SVTOOL" contains a failed migration to version 13 !
            at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1578)
            at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:545)
            at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482)



  • 2.  Re: Error creating bean with name 'dradisInitBean'

    Broadcom Employee
    Posted Jun 26, 2017 09:41 AM

    Is this a brand new install using a new Enterprise Dashboard database on Oracle or an upgrade from an earlier version using the same database?



  • 3.  Re: Error creating bean with name 'dradisInitBean'

    Posted Jun 26, 2017 09:52 AM

    Marcy, this is a new install of 10.1 Enterprise Dashboard on a Linux Redhat server using Oracle for the database.



  • 4.  Re: Error creating bean with name 'dradisInitBean'

    Broadcom Employee
    Posted Jun 26, 2017 10:03 AM

    Did you make sure the database was created with an UTF-8 character set?



  • 5.  Re: Error creating bean with name 'dradisInitBean'

    Posted Jun 26, 2017 10:08 AM

    I believe it is set to utf-8 but I will verify that fact.  I will get back as soon as I can.



  • 6.  Re: Error creating bean with name 'dradisInitBean'

    Broadcom Employee
    Posted Jun 26, 2017 10:15 AM

    This link might help:

    Tech Tips: What are the BEST PRACTICES for DevTest Database Troubleshooting 

     

    Also:

    The character set must be Unicode set. For the initial creation of the database, the Oracle user must have the CREATE VIEW system privilege. Oracle must be installed with UTF8 encoding.



  • 7.  Re: Error creating bean with name 'dradisInitBean'

    Posted Jun 26, 2017 10:27 AM

    We are checking with the dba's but it may be tomorrow due to the difference in time zones.

    Thanks.



  • 8.  Re: Error creating bean with name 'dradisInitBean'

    Posted Jun 26, 2017 11:33 AM

    Character set is set for UTF-8 and privileges are set to have create view for the id we are using.



  • 9.  Re: Error creating bean with name 'dradisInitBean'

    Posted Jun 26, 2017 01:00 PM

    Did the DBA allow DevTest privileges to create the tables in both the Enterprise Dashboard AND the Registry schemas or did a DBA create the tables from the supplied DDL?

     

    Once the tables have been initialized, DevTest needs CRUD priveleges in order to add, update, delete entries.  As MarcyNunns stated, Tech Tips: What are the BEST PRACTICES for DevTest Database Troubleshooting is a good resource as well as Configure Enterprise Dashboard to Use Oracle - DevTest Solutions - 10.1 - CA Technologies Documentation    

     

    For reference, this graphic shows the characterset I have used with Oracle in the past.  Generally, I let DevTest create the tables after the schema has been created and set the privileges to CRUD once the tables are successfully created.



  • 10.  Re: Error creating bean with name 'dradisInitBean'

    Posted Jun 26, 2017 01:12 PM

    Joel, thanks for the input.  Dba' used the dll to create the tables.  We will look thru the sources you mentioned. 



  • 11.  Re: Error creating bean with name 'dradisInitBean'

    Posted Jun 26, 2017 01:29 PM

    Before starting the Enterprise DB service,

    - verify the login user account privileges (i.e., CRUD + create View)

    - go into logging.properties and set the logger to DEBUG and add the additional logging properties from the troubleshooting guide (i.e., log4j.logger.com.mchange.v2.c3po=DEBUG, and the other one)

    - go into lisatmp_10.1.0 and remove the enterprisedashboard.log file, if it exists so you only see the most current log entries

    - start the Enterprise Dashboard service

    - watch the log file

    If the service starts, then do the same on Registry service.

    If Registry starts, you can edit the logging.properties file back to INFO, and start the remaining services one-by-one (i.e., Broker, Portal, Coordinator, Simulator, VSE, etc.) to ensure they all come up correctly

     

    NOTE: I believe you already know this, but the Enterprise Dashboard DB is in one schema and the Registry DB is in a different schema. They can both be in the same Oracle database, but they must be in different schemas.



  • 12.  Re: Error creating bean with name 'dradisInitBean'
    Best Answer

    Posted Jun 29, 2017 11:38 AM

    Marcy and Joel, Thanks for the input between all your comments we have been able to get 10.1 up.  We ended up clearing out all the tables build by the dba using the dll and made changes to the multiple property files.

    Brent.