Help with note 1539125 via PowerShell
Good afternoon, colleagues.
I apologize for my English =)
One day I decided to adjust the tool Sybase in accordance with the recommendations of SAP on the note 1539125. And the first one I had, it’s uncomfortable, the console output tool Sybase in which I had to look up the settings and check their value and required. Using transaction DBACOCKPIT is not very convenient, given that I have about 6 instances on the tool Sybase. All this becomes a routine work. I spent a little time here and wrote a script in PowerShell. He asks for parameters tool Sybase selects only the needed values and compares them with the required values. All this in a html table which matches are marked in green, and does not correspond to the red, for clarity. After which generates DDL script, which sets all the required parameters. In this script, all parameters, even those corresponding to the desired value, it is convenient in the case of Run this script in other instances. Then you can do part of the script that generates the report and see whether to apply the settings. Well, that’s it, enclose the script and the sample parameter file database, it all units are those that are used in the tool Sybase.
In addition, you will need to install the driver Sybase ODBC(you can download from sybase.com) on the machine which will run the script. Only no circumstances should you install the ODBC driver on the server is running Sybase ASE!
And for the full implementation of the sql script, it needs to be run as user sa.
Sample of HTML report:
P.S. The script is not perfect, but life easier =)
Nice, thanks for sharing this.
Powershell is not something I have used, but this looks interesting.
BTW, there will be an ODBC driver already registered on the application server (which may be the DB server also) as it will be used to connect to the ASE, so in theory it should work directly from there. Was this something you tried?
I've tried does not work. On the server where the Sybase ASE is installed, the driver is being used by a tricky way, it is not registered in the system and therefore can not use it through powershell. If you experience any problems in the script, write, I will be glad to help. Personally, I like it greatly facilitated the work =)
Good point, I think it moved to the point where it loaded the driver directly without using the ODBC driver manager, which would explain why it didn't work - and also why you correctly say to not install a further driver on the server.
I do not know how to use the ODBC driver directly through powershell, if you are able to do the share. In this case, it will work. =)