Vault Pro, Keyword Expansion - Oracle Forms PL/SQL Libraries

[clarkec21]

Hi

I am having trouble with Keyword Expansion upon checkin of Oracle Forms PL/SQL Library (*.pll).

I am using the notation '$Revision: 1 $' in exception handling within functions and procedures that is used to log the version number of the library in an Oracle table by function call as follows:
EXCEPTION
WHEN OTHERS THEN
pa_err_msg := SQLERRM;
pr_log_message_lib( pa_mdl_name => 'WRK_L010'
, pa_mdl_version => '$Revision: 1 $'
, pa_error_code => SQLCODE
, pa_location => 'fn_cancel_monitor_by_id '||l_loc
, pa_text => pa_err_msg||' PARAM pa_monl_id : '||pa_monl_id
, pa_severity => 'E'
) ;
RETURN 'FAILURE';

When checking in the replacement does work and the version number matches the Vault version (I can see by opening the file in textpad) but the pll file will then no longer open in Oracle Forms Builder - I get the error "PDE-PER001 Internal error (depli 36)". Exactly the same issue happens with VSS 6.0 - any ideas?

[lbauer]

What keyword(s) are you expanding in these files?

Are the .pll files binary?

[clarkec21]

Hi Linda - I am using '$Revision: 1 $' - The '.pll' has been added to the list of mergeable files and added to the keyword expansion list with no Start or End of History line markers.

Yes the file is binary. Is this the problem? We do the same with Oracle Forms and have no problem, the revision works and the form is not corrupted. When checking the *.pll files in and out of SGV without '$Revision: 1 $' there is no corruption.

I have noticed when I open the *.pll file using a text editor there are embeded '$' chars.

[lbauer]

Our implementation of Keyword Expansion is similar to VSS. A binary file can be corrupted by keyword expansion, especially if the keyword expands to a different string length each time.

You might be able to use keywords if you keep the expanded keyword at a consistent spacing.

Instead of this:

Code: Select all

$Revision: 1 $

Try:

Code: Select all

 $Revision::       1 $ 

Leave enough space to account for the longest possible string length.

When you use one colon, Vault puts its information between the colon and the dollar sign. Depending on how long the information is, and how many spaces you had, this can make the whole string either shorter or longer than it was at first. In a text file, this is not a problem, but will corrupt a binary file.

When you use two colons, Vault keeps the string length the same. Vault maintains the exact same number of characters between the second colon and the dollar sign. Vault adds extra spaces, or truncates the information, as necessary, in order to keep things the same, so the binary file is not corrupted.

Note: You can't use this for the History or Log keywords.

[clarkec21]

Linda, that worked perfectly, Thank you very much for that.

[lbauer]

Thanks for the update. That's good news.