Oracle Hello World: Designer looses all Procs in Catalog Explorer

Posts   
 
    
ianvink
User
Posts: 393
Joined: 15-Dec-2006
# Posted on: 21-Oct-2020 01:37:16   

v5.4 , RTM, Oracle 11.2

In the designer, we connect a number of stored procedures, then map them to TypesViews and Proc calls

Then we open the Sync Relational Model Data dialog again, choose another proc, then update.

The Designer removes all of the previous Stored Procedures (see screen shot) and returns "Sequences", see screenshot

When the Relational Model Data Retrieval Wizard appears, there are no checked items beside the previously selected procs. It 'forgets' about them.

We get lots of these errors:

Stored procedure call 'Apps.XxWebInventoryPkgGetSellableInventory'
Sync::              Stored procedure call 'Apps.XxWebInventoryPkgGetSellableInventory' is no longer mapped to a target as target storedprocedure 'APPS.XX_WEB_INVENTORY_PKG.GET_SELLABLE_INVENTORY' was not found in the catalog.
Attachments
Filename File size Added on Approval
2020-10-20_16-36-27.jpg 364,732 21-Oct-2020 01:37.33 Approved
Otis avatar
Otis
LLBLGen Pro Team
Posts: 39588
Joined: 17-Aug-2003
# Posted on: 21-Oct-2020 09:30:59   

In the screenshot your catalog name is different from what it was, as the error states, so as the new catalog is empty, it can't find the original one back and removes the mapping.

If you refresh with schema data from another catalog/server, be sure to first rename the catalog/server in your project to the one you want to refresh with, then refresh the project

Frans Bouma | Lead developer LLBLGen Pro
ianvink
User
Posts: 393
Joined: 15-Dec-2006
# Posted on: 21-Oct-2020 17:22:36   

Hi,

When I create the connections I use:

databaseurl:1551/schema (notice the colon)

Then LLBL says this is in error as ":" is an illegal character so renames by changing ":" to "_" when I Sync

databaseurl_1551/schema

Actions taken for catalog 'xxxxxxx.local_1551/ERPUAT' Warning: 'The catalog name 'xxxxxxx.local:1551/ERPUAT' was renamed to 'xxxxxx.local_1551/ERPUAT' because it contained an illegal character, like ':'. Please rename the catalog in the database's management system.'

Is that the error? Note that I can not change the database.

ianvink
User
Posts: 393
Joined: 15-Dec-2006
# Posted on: 21-Oct-2020 17:46:39   

Using a tnsnames.ora to create an alias in C:\Oracle\network\admin fixed the issue as LLBL didn't have to rename. We now connect to "MyLLBLOracleAlias"

This might be a bug? By using an Oracle connection to a non-default port like "databaseurl:1551/schema" causes LLBL to rename the catalog and then lose the sync.