" /> ETL Not Transferring after production DB Restore - Genesys CTI User Forum

Author Topic: ETL Not Transferring after production DB Restore  (Read 4917 times)

Offline PFCCWA

  • Hero Member
  • *****
  • Posts: 655
  • Karma: -7
ETL Not Transferring after production DB Restore
« on: August 30, 2012, 03:18:55 PM »
Advertisement
Hello,

We have restored the etl and ods production databases into our test sql server however experiencing issues running the etl trans_once and trans_only batch files.
Looking at the etl service logs I can see the batch file being executed (in this example trans_only) however it fails with the error below.
There is a reference to the DM_PROPERTY table within the datamart database without explicitly advising what the problem is.
I also noticed that when the transform is executed there is reference to the ODS database sql user, with the etl database.  This is repeated on the Main.Options line.  I am sure this should be the etl database sql user, not ods.
Checked the etl properties file, and both Datamart and ods DAP's.
Data chunks are being generated in DMA, just not transferring.
Can load and view tables in ETL Assistant.
Thanks.

Starter: Starting 'ETL_Trans_Only' on  Thu Aug 30 16:02:00 2012
Starter: Current directory is set to .
Starter: Executing "java -Xmx256m -jar transform.jar -conf etl.properties -loglevel=WAKE:3,START_WRITE_MON:3,DROP:9,WRITE:3,INFO:9,PURGE:9,WARNING:8,ERROR:9,_ALL_:0 -maxNumberOfChunksInReadQueue=10 -maxNumberOfChunksInWriteQueue=20 -maxNumberOfConnToDist=2 -jdbcurl=jdbc:jtds:sqlserver://{dbhost}:{dbport};DatabaseName:{etldbname} -user={odsdbuser} -passEncrypted=******"
Starter: Pipe 360 "\\.\pipe\054840000024931_CCA" and Event 136 created for ETL_Trans_Only
Starter: waiting for a client to connect to the pipe 360.
Starter: client connected to the pipe 360.
Starter: Thu Aug 30 16:02:00 2012 [ETL_Trans_Only] will be started on Thu Aug 30 16:03:00 2012 start in 60 seconds
ETL_Trans_Only*:* Time        Origin                    Message
ETL_Trans_Only*:* ------------ -------------------------- ----------------------------------------
ETL_Trans_Only*:* 16:02:00.268 Main ETL Runtime, Version: 7.2.100.00, Build: 2008/04/29 12:34 (C) Copyright 1994-2008 Genesys Telecommunications Laboratories, Inc.
ETL_Trans_Only*:* 16:02:00.659 Main.Env Runtime info: {java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition, sun.boot.library.path=C:\Program Files (x86)\Java\jre1.5.0_18\bin, java.vm.version=1.5.0_18-b02, java.vm.vendor=Sun Microsystems Inc., java.vendor.url=http://java.sun.com/, path.separator=;, java.vm.name=Java HotSpot(TM) Client VM, file.encoding.pkg=sun.io, sun.java.launcher=SUN_STANDARD, user.country=US, sun.os.patch.level=Service Pack 2, java.vm.specification.name=Java Virtual Machine Specification, user.dir=D:\Program Files (x86)\GCTI\Data Mart\etl_service\etl_runtime, java.runtime.version=1.5.0_18-b02, java.awt.graphicsenv=sun.awt.Win32GraphicsEnvironment, java.endorsed.dirs=C:\Program Files (x86)\Java\jre1.5.0_18\lib\endorsed, os.arch=x86, java.io.tmpdir=C:\WINDOWS\TEMP\, line.separator=<CR><LF>, java.vm.specification.vendor=Sun Microsystems Inc., user.variant=, os.name=Windows 2003, sun.jnu.encoding=Cp1252, java.library.path=C:\WINDOWS\system32;.;C:\WINDOWS\system32;C:\WINDOWS;C
ETL_Trans_Only*:* 16:02:00.659 Main.Options Options: {maxNumberOfChunksInWriteQueue=20, maxNumberOfChunksInReadQueue=10, passEncrypted=B42CB10656F6B589, loglevel=WAKE:3,START_WRITE_MON:3,DROP:9,WRITE:3,INFO:9,PURGE:9,WARNING:8,ERROR:9,_ALL_:0, user={odsdbuser}, CfgUser=default, maxNumberOfConnToDist=2, CfgAppName=ETL_Proxy, CfgUserPassword={defaultpassword}, dropTransferredTables=, pass=*****, jdbcurl=jdbc:jtds:sqlserver://{dbhost}:{dbport};DatabaseName:{etldbname}}
ETL_Trans_Only*:* 16:02:00.675 Main TRANSFORM started
ETL_Trans_Only*:* 16:02:00.831 Main Unhandled exception happened. Exiting ...
ETL_Trans_Only*:* 16:02:00.831 Main Stack Trace:
ETL_Trans_Only*:* 16:02:00.831 Main common.TransformError: Error during upgrade
ETL_Trans_Only*:* 16:02:00.831 Main at ETL.UpgradeOfficer.approve(UpgradeOfficer.java:172)
ETL_Trans_Only*:* 16:02:00.831 Main at ETL.Transformer.start(Transformer.java:77)
ETL_Trans_Only*:* 16:02:00.831 Main at ETL.Transformer.main(Transformer.java:199)
ETL_Trans_Only*:* 16:02:00.831 Main Caused by:
ETL_Trans_Only*:* 16:02:00.831 Main SQLState: S0002
ETL_Trans_Only*:* 16:02:00.831 Main Vendor:  208
ETL_Trans_Only*:* 16:02:00.831 Main Stack Trace:
ETL_Trans_Only*:* 16:02:00.831 Main java.sql.SQLException: Invalid object name 'DM_PROPERTY'.
ETL_Trans_Only*:* 16:02:00.831 Main at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)
ETL_Trans_Only*:* 16:02:00.831 Main at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2816)
ETL_Trans_Only*:* 16:02:00.831 Main at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2254)
ETL_Trans_Only*:* 16:02:00.831 Main at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:631)
ETL_Trans_Only*:* 16:02:00.831 Main at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQLQuery(JtdsStatement.java:477)
ETL_Trans_Only*:* 16:02:00.831 Main at net.sourceforge.jtds.jdbc.JtdsStatement.executeQuery(JtdsStatement.java:1301)
ETL_Trans_Only*:* 16:02:00.831 Main at ETL.UpgradeOfficer.approve(UpgradeOfficer.java:137)
ETL_Trans_Only*:* 16:02:00.831 Main at ETL.Transformer.start(Transformer.java:77)
ETL_Trans_Only*:* 16:02:00.831 Main at ETL.Transformer.main(Transformer.java:199)
Starter: Waiting for process [ETL_Trans_Only] to exit...
Starter: Process [ETL_Trans_Only] has terminated with exit code 3

Offline Timur Karimov

  • Sr. Member
  • ****
  • Posts: 415
  • Karma: 2
Re: ETL Not Transferring after production DB Restore
« Reply #1 on: August 30, 2012, 04:47:33 PM »
Hi,
from you log file i see this SAQL connection settings:

jdbcurl=jdbc:jtds:sqlserver://{dbhost}:{dbport}

Is it real data in you etl options or you jus remove real server name from log for security reason?

WBR Tim

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: ETL Not Transferring after production DB Restore
« Reply #2 on: August 30, 2012, 05:03:35 PM »
Does the table is still there on the DBServer?

Offline PFCCWA

  • Hero Member
  • *****
  • Posts: 655
  • Karma: -7
Re: ETL Not Transferring after production DB Restore
« Reply #3 on: August 30, 2012, 08:48:03 PM »
[quote author=Timur Karimov link=topic=7399.msg31656#msg31656 date=1346345253]
Hi,
from you log file i see this SAQL connection settings:

jdbcurl=jdbc:jtds:sqlserver://{dbhost}:{dbport}

Is it real data in you etl options or you jus remove real server name from log for security reason?

WBR Tim
[/quote]

I have removed the real server name and port for security reasons.
and the table (DM_Proprty) exists on the datamart (etl) database, i opened it and could see things like agg date, trans data, datamart version.
Could be a conflict from restoring the db from production in UAT but logs are not being specific enough to determine where the issue is.
thanks.

Offline Timur Karimov

  • Sr. Member
  • ****
  • Posts: 415
  • Karma: 2
Re: ETL Not Transferring after production DB Restore
« Reply #4 on: August 30, 2012, 09:01:52 PM »
Which DB r u use? Oracle? MS SQL? anyway - ask the DBA to check the ownership of you restored DB.
Last two issues with such error what i see at my customers - all belong on DBA side not the Genesys.

HIH
WBR Tim


Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: ETL Not Transferring after production DB Restore
« Reply #5 on: August 30, 2012, 09:36:46 PM »
Ahh I remember having the same issue...you see after a MSSQL restore the user on the DB is orphan because the user is not linked to anything on the DBServer itself as the ID is missing.
So you have to do this:
http://support.microsoft.com/kb/274188

Offline bandorka

  • Full Member
  • ***
  • Posts: 120
  • Karma: 1
Re: ETL Not Transferring after production DB Restore
« Reply #6 on: August 31, 2012, 06:34:34 AM »
The owner of the table is correct?