Hi,

The second step allow you to select what document classes you want to move from the source to the target repo. Perhaps you have missed the fact that a document repo can contain documents with several different classes?

/Mathias

PS. If the documentation is not clear about this, please file a case via our support and we will make sure it becomes clearer. Please suggest also what is not clear.

Thanks!

Thank you for your reply Mathias,

Please see screenshot below, I thought the the document class was specified when you create the line in the IFS Windows below?

Miguel

Yes. But if you use * for document class, then “all other classes” (that does not have its own repo) ends up in that one. Hence a repo can have many classes, and that is why we present an option for it :)

I understand that, I am just confused about the sequence of events around creating the repository lines in the first place.

I mentioned in my original post that the second step of the wizard does not give me a LOV with our document classes, what do I do about that?

Thanks

There should not be a LOV there since you should not select any classes by entering them manually. The second step should show you the number of documents in each class that exists in that repo and you select which classes to move using the checkbox. Perhaps, if you are just playing around, you found a bug where it does not work well if there are no documents at all in that repo?

I see what you did now, you added a new line in the second step. Don’t do that! Probably my guess above is correct, there are no documents in that repo and the step did not take that scenario into account. If you like you can file a support case about this confusing behavior.

I will work through the wizard again without creating the line in the repository and I let you now how it goes.

Many thanks for your advice

Miguel

Hi,

Please see below. I have ignore step 2 of the wizard

Could you please confirm that this looks OK?

I only have 2 documents in Class APPE that I am happy to move from the Database to the FTP server.

Now I get to step 3 however I don’t have steps 4 and 5 available?

Thanks

Miguel

I am concerned about the first screenshot (page 1/5 of the wizard) now showing the description of the Repository. Certainly I don’t want to move 600 GB worth of documents to the FTP so I must make sure that only the documents in Class APPE are to be moved

thanks

Miguel

OK, I see the repository description is blank in my settings. However, I need to make sure that only the class specified in APPE_R1 is going to be moved and the Wizard is not showing me much info about number of documents to be moved, etc.

Miguel

Are there any documents in APPE_R1?

APPE_R1 is linked to doc class APPE and we have 3 documents in the class as shown below

Was those documents there already when you created the APPE_R1 repo? If yes, then they reside in one of the other repos.

yes, so they reside in our DATABASE repository, which is in status Generating.

I thought the process described would allow me to pull them from the DATABASE repo, obviously I have got that wrong. 

I am still stuck though, how do I move documents from the DATABASE repo to an FTP repo using the wizard?. It doesn’t look possible to move documents from a repository in status Generating, please see screenshot, only repos in status Usable are available in the first step of the Wizard.

Do I have to change the status of the DATABASE repository to usable, is that advisable?

Thanks

Miguel

I think you should read the documentation on how that assistant works. It’s actually quite detailed. Press the F1 key on your keyboard, it’s your friend :)

I suggest that you create a test class and a test repository of type Database. Then create some documents of that class. Then set that test repository to Usable and try a move.

OK, I will try that, thank you later today.

Please see below from F1, I don’t see any references about how to  move documents from the BLOB/Database to an FTP repo and how to deal with the generating and usable status

“Use step 1 to move files from one repository to another.If the wizard is launched from the navigator, then it is possible to select which repository to move from and which repository to move to. But if the wizard is launched through a right mouse button operation, it is not possible to select which repository you should move from this will be automatically selected depending on which repository or document class you launch the wizard from. The Move From Repository area has default list of repositories which are in Usablestate. The Move to Repository area has default list of repositories which are in Generating state. When the repository ID is selected, the rest of the values are automatically updated.”

It does not mention any specific type of repository since it should work the same way regardless of the repository type. It mentions that the from repositories are in Usable state and the to repositories are in Generating state. Perhaps it could have been clearer, not sure. If you like, file a support case and we will try to make sure the documentation is clearer on this subject.

Hi Mathias,

I have changed the status of the BLOB repository (Database) to Usable., then save.

Then I used the Change Document Repository wizard and I can see the DEFAULT repository as an option on the first section on page 1 of the Wizard.

However in the second screenshot you can see how I am not able to select a document CLASS in the DEFAULT repository to be moved to a chosen new repository. There isn’t a list of values with all the classes available in the DEFAULT repository. We do have many document classes in the BLOB.

So, I am still not able to move document classes from our BLOB to an FTP server.

Could you please advise when you have a minute?

Many thanks

Miguel

Hi,

I cannot explain what you describe. Step two should show a list (not in a LOV) of document classes that are stored in DEFAULT, and the number of documents in each class. Perhaps some bug, not sure.

Can you do this:

• Start the Debug Console
• Start the assistant again, like you did above
• Go to the second step
• Look in the Debug Console and try to identify the SELECT that runs to populate the list of document classes.
• Copy and paste the SELECT here.

Perhaps we can see what is wrong and perhaps you will also get a clue from how the SELECT looks and what input it uses, or from any result (it looks like there are no hits, but we’ll see).

If this does not give a clue, perhaps it is better to file a support case such that someone can do a more focused effort of helping out.

/Mathias

Hi Mathias,

Thank you for your reply. Please see below

I think this is the Page 1/5 corresponding code:

BEGIN DECLARE sLocType VARCHAR2(30); BEGIN :p0 := &AO.EDM_LOCATION_API.Get_Description( :p1 ); :p2 := &AO.EDM_LOCATION_API.Get_Location_Type( :p1 ); sLocType := &AO.EDM_LOCATION_API.Get_Location_Type( :p1 ); :p3 := &AO.EDM_LOCATION_TYPE_API.Encode(sLocType); :p4 := &AO.EDM_LOCATION_API.Get_Location_Status( :p1 ); END; 
EXCEPTION 
WHEN &AO.Error_SYS.Err_Security_Checkpoint THEN 
raise; 
WHEN OTHERS THEN 
rollback; 
raise; 
END;

and I think this is the page 2/5 corresponding code:

select OBJID, OBJVERSION, DOC_CLASS, &AO.DOC_CLASS_API.Get_Doc_Name(DOC_CLASS), &AO.EDM_FILE_API.Get_File_Count(DOC_CLASS, LOCATION_NAME), LOCATION_NAME from &AO.EDM_LOCATION where ( LOCATION_NAME = 'DEFAULT' AND DOC_CLASS IN( SELECT DISTINCT DOC_CLASS FROM &AO.EDM_FILE WHERE LOCATION_NAME = 'DEFAULT' ))

if I run that last SQL statement in SQL Developer I don’t get any results either

That SQL does not look right. 

Seems the scenario where you move from the * repo is not covered. I think the reason is that, when this feature was added, the primary scenario was to move from class-specific repos to one central, in the database.

In theory you could workaround this limitation/bug by manipulating the repository table (edm_location_tab) as well as the table where all file references are stored, to “fit” the SQL.

Basically you would add one “new” repo per class that is already stored in your DEFAULT repo, and change the repo (location_name) in the file reference table (edm_file_tab) to match.

I think you have found a bug, and I think you should report it.

Thank you for your help Mathias. 

I will report this bug.