You are viewing limited content. For full access, please sign in.

Question

Question

Laserfiche Repository SQL Migration

Laserfiche
Updated February 3, 2021
asked on November 18, 2020 • Show version history

Hi All,

 

 

I am trying to migrate Laserfiche repository from Oracle to SQL server.

 

I am trying to map the existing repository in Oracle to SQL server but it says UUID already exists.

 

Can someone help?

 

0 0

Replies

replied on November 19, 2020

Hi Mehak, 

Can you please open a support case? I believe there is a small utility required to resolve the "UUID already exists" error that Laserfiche Technical Support can provide.

You can reference this Answers post when you open the support case. 

Best, 

Sam

0 0
replied on November 25, 2020

Sure, Sam. That would be great.

replied on November 24, 2020 • Show version history

Hi Samuel,

 

Thanks for getting back. Just one question I have: If we have the current repo of Laserfiche 9.2 on Oracle and now want it to move to SQL Server.

We have got the contents moved by our DBA team using the Microsoft process, what will the steps to mount the existing repo with the SQL server with all the contents?

 

Is running UUID updater the best option or we have any other way-outs?

By running UUID updater I am currently getting errors, hence just want to check if it's the right way to go.

0 0
View 3 previous replies
replied on November 24, 2020 • Show version history

Hi Mehak,

If you let Support know the error the UUID Updater utility is throwing they should be able to help you determine the right way to proceed. I know there is both an older, official UUID Updater utility that had a few issues along with a newer beta one that fixes some of those issues. Depending on the error you're getting, the new beta UUID Updater might address that specific problem.

0 0
replied on November 24, 2020

Thanks, Samuel but is the right approach that we are following?

 

I just want to raise a ticket once I am sure if what I am doing is right?

 

Below is the error though:

 

2020-11-24 17:15:04.343 SQL error encountered: SQL ERROR: [Microsoft][SQL Native Client][SQL Server]Invalid object name 'dboptions'. SQL STATEMENT: 敳敬瑣漠瑰潩癮污敵映潲扤灯楴湯⁳桷牥⁥灯楴湯慮敭㴠㼠†††††††††† 2020-11-24 17:15:04.343 Update failed.

0 0
replied on November 24, 2020

I haven't done the Oracle -> SQL Server migration myself so I unfortunately couldn't tell you if what're doing is right. I don't recognize the error either.

I'd open the support case and provide a link to this Answers thread along with any other information you can share about what you've done so far. They should be able to point you in the right direction.

0 0
replied on November 25, 2020

Sure, Sam. That would be great. Please let me know if you get any updates.

For now, I just created a blank repo and connected it to the new SQL server.

We have an existing repo on Oracle which is now on SQL server using the Microsoft recommended transfer steps.

We need to register the existing repository with SQL and see if it mounts and we are able to see the documents.

0 0
replied on December 1, 2020

Hi Mehak,

To clarify, you'll need to ask your Solution Provider (looks to be Ricoh Australia) to open the support case on your behalf.

0 0
replied on February 3, 2021

Hi Mehak,

As the manager for the Australasia region, I would be happy to assist you guys and get you the support that you need. Please reach out to me at scott.song@laserfiche.com for further follow-up.

Best,

Scott 

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...