Skip to main content
Question

Truncate non-versioned oracle table hanging forever

  • August 10, 2018
  • 4 replies
  • 22 views

Forum|alt.badge.img

I am trying to copy the data from our staging database to our production, but it hanging at this stage forever (more than 12 hours now).

35.9| 0.1|INFORM|Geodatabase Writer: Truncating table/feature class `GEODBMGR.Assess_Parcels'

I don't see any error message. It used to work. This is first time I run it after I clicked the 'Update writer'. I don't know if that has anything to do with this.

Thank you in advance for any of your help!

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

4 replies

xiaomengatsafe
Safer
Forum|alt.badge.img+11
  • Safer
  • 324 replies
  • August 10, 2018

Hi @alicepingxue, sorry that you are experiencing this problem. We want to investigate whether updating the writer caused problems. It would be really helpful if you could provide the following:

  • A copy of the workspace from before the writer was updated.
  • A log file from a previous successful run (before writer update)
  • The current workspace exhibiting the problem
  • Log from the current workspace.

You can add these files as attachments by posting a comment or answer to this question. Or if you have concerns about sharing your workspace and log in the Q&A; forum, please send it to us directly through this web form, and reference this Q&A; post.

Looking forward to hear from you. Thank you very much!


Forum|alt.badge.img
  • Author
  • 1 reply
  • August 11, 2018

Hi @alicepingxue, sorry that you are experiencing this problem. We want to investigate whether updating the writer caused problems. It would be really helpful if you could provide the following:

  • A copy of the workspace from before the writer was updated.
  • A log file from a previous successful run (before writer update)
  • The current workspace exhibiting the problem
  • Log from the current workspace.

You can add these files as attachments by posting a comment or answer to this question. Or if you have concerns about sharing your workspace and log in the Q&A; forum, please send it to us directly through this web form, and reference this Q&A; post.

Looking forward to hear from you. Thank you very much!

Hi Xiaomeng, where can I find the log file from a previous run? Thanks!

 

 


xiaomengatsafe
Safer
Forum|alt.badge.img+11
  • Safer
  • 324 replies
  • August 13, 2018
Hi Xiaomeng, where can I find the log file from a previous run? Thanks!

 

 

Hi Alice, The log from previous run would likely be replaced by the new log, if you didn't save a new copy of the workspace, after updating the writer. No worries.

 

However, I am curious about the timeline discrepancy in the log. Would you mind using the attachement method to attach your finished log file? So we can investigate.

 

At a glance, the translation looks to have taken 1 day and 18 hours, to complete, but the CPU time only adds up to about 2.3 hours. I'm hoping the full log will tell a more complete story of what happened. Thank you!

 


xiaomengatsafe
Safer
Forum|alt.badge.img+11
  • Safer
  • 324 replies
  • August 13, 2018
Hi Xiaomeng, where can I find the log file from a previous run? Thanks!

 

 

Also, @alicepingxue, can you please also attach your workspace itself? Thanks!