Gary_Shaw
4th December 2007, 23:00
I noticed that the 8.4a porting set allows one to use the combo driver on unix systems. Has anyone given this a try? Any good news or bad?
I will be moving to new hardware and porting set in the coming months and was considering using it.
Dikkie Dik
4th January 2008, 17:05
A small benchmark resulted in a 5% CPU improvement. For 8.4b some internal layers communication layers will be stripped and so another few percentages can be gained.
No significant improvements, but improvements over all applications.
I haven't seen any negative thing so far.
Hope this helps,
Dick
dave_23
9th January 2008, 20:05
I just tested it on our system. It doesn't cross databases, you'll get a 505 error if the system needs to talk to another DB. Or, if you leave the "s" line in the ipc_info it will spawn a new oracle driver.
So, not particularly helpful for me.
Dave
Gary_Shaw
9th January 2008, 20:09
Thanks Dave,
Crossing databases would be an issue for me as I have archive companies in another database.
dave_23
9th January 2008, 20:27
That's probably ok as long as the bulk of your processing is in the one DB.
if it forks a driver to handle the Archive company lookup no big loss.
For me, it will log-in combo mode to Tools and then fork a driver to handle my company specific stuff.. which doesn't help me any.
Dave
Dikkie Dik
9th January 2008, 23:43
If you need multiple database drivers, you can specify:
oracle8 d ora8_srv6.2
oracle8 s ${BSE}/bin/ora8_srv6.2
Then it will first start a combo driver and the 2nd driver will be a "normal" driver.
If you have start the database first some queries on company 000 will activate in above case a combo driver for company 0 and an additional process for other drivers. To prevent this you can think about:
tabledef:
*:000:oracle8(ORACLE_SID=ERPLN)
*:*:oracle8c(ORACLE_SID=ERPLN)
ipc_info:
oracle8 s ${BSE}/bin/ora8_srv6.2
oracle8c d ora8_srv6.2
oracle8c s ${BSE}/bin/ora8_srv6.2
Hope this helps,
Dick