• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • Any generic best default Oracle 12 connection parm settings?

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (2)

Resolved Any generic best default Oracle 12 connection parm settings?

  1. Issue
0
Votes
Undo
  1. David Sternberg
    David Sternberg
  2. PowerBuilder
  3. Friday, 8 June 2018 15:48 PM UTC

Using Oracle 12 with Appeon PB trying to be anal about runtime connection parms (mostly run thru Citrix).  Do you have any comments on existing settings below or recommendations to consider adding as a general "best" default?  Note for Sybase I used to append the user id to the app name parm so I could tell who was running on the server but not for Oracle.

DBParm = PWDialog = 0, PBCatalogOwner='data_schema_owner', CommitOnDisconnect = 'No', NcharLiteral = 'Yes', BindSPInput = 1, DelimitIdentifier = 'No', Appname = 'App Name'

  1. Oracle
  2. PowerBuilder
Error when Minimizing a Powerbuilder Web App.
Any functionality in PB to allow just one instance...
Accepted Answer
David Sternberg
David Sternberg Accepted Answer Pending Moderation
  1. Tuesday, 12 June 2018 18:10 PM UTC
  2. PowerBuilder
  3. # Permalink

I expected my post was a loaded question and much is left in the eyes of the beholder with various ways to achieve desired goals.  Further I guess most parameters are parameters because there are reasons to have various values under different philosophies and situations.

Comment
There are no comments made yet.
Responses (2)
David Peace (Powersoft)
David Peace (Powersoft) Accepted Answer Pending Moderation
  1. Friday, 8 June 2018 16:10 PM UTC
  2. PowerBuilder
  3. # 1

Hi

We use this a code to set detail sin the module, we put the appname and version in the string. This allows us to check the version in the DB and prevent people updating data if they do not have the right version.

 

declare p2 procedure for
      DBMS_APPLICATION_INFO.SET_MODULE
      (:app_name,'Running') using SQLCA;
        
EXECUTE p2;

Hope that helps.

Cheers

David

Comment
David Sternberg
  1. David Sternberg
  2. Friday, 8 June 2018 19:42 PM UTC
Thank you, but consider I code for app and db version protection differently.  I place the version in the app ini file that the exe uses to get the dbparm values and have the app version also in a db table.  Upon app connection, these two version values (ini / exe against db) are matched before the application opens, otherwise the user is informed to install the correct version of the application.

  1. Helpful
David Peace (Powersoft)
  1. David Peace (Powersoft)
  2. Monday, 11 June 2018 08:37 AM UTC
That's fine and typically how we check DB version too, but on large 24/7 systems we can upgrade the DB with users live and they get prompted to install the new version but can carry on read only in the meantime.



The point is that you can store anything you line n the Module and pick this up in code for use later.



Cheers



David

  1. Helpful
David Sternberg
  1. David Sternberg
  2. Tuesday, 12 June 2018 18:08 PM UTC
Thank you.  I expected my post was a loaded question and much is left in the eyes of the beholder with various ways to achieve desired goals.  Further I guess most parameters are parameters because there are reasons to have various values under different philosophies and situations.  Thanks again for responding and have a great day.

  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.