38514 - Java.sql.SQLException can occur when renaming variables in the Configuration tree of the SAS® Risk Dimensions® 5.2 Java Client

Problem Note 38514: Java.sql.SQLException can occur when renaming variables in the Configuration tree of the SAS® Risk Dimensions® 5.2 Java Client

When re-naming variables in the Configuration tree, the SAS Risk Dimensions 5.2 Java Client might generate a java.sql.SQLException error like the following:

java.sql.SQLException: Cannot perform reqested operation. ResultSet not open.
	at
com.sas.rio.MVALocalizedError.throwLocalizedException(MVALocalizedError.java:196
)
	at
com.sas.rio.MVALocalizedError.throwLocalizedException(MVALocalizedError.java:146
)
	at com.sas.rio.MVAResultSet.absolute(MVAResultSet.java:450)
	at sun.reflect.GeneratedMethodAccessor91.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at com.sas.analytics.jdbc.ResultSetProxy.invoke(ResultSetProxy.java:33)
	at $Proxy3.absolute(Unknown Source)
	at com.sas.analytics.jdbc.JDBCTable.absolute(JDBCTable.java:192)
	at com.sas.analytics.jdbc.JDBCTable.getObjectAt(JDBCTable.java:70)
	at com.sas.analytics.jdbc.JDBCTable$Column.get(JDBCTable.java:391)
	at com.sas.analytics.cmp.util.SortedList.get(SortedList.java:209)
	at com.sas.analytics.cmp.util.IndexedList.get(IndexedList.java:452)
	at com.sas.analytics.cmp.util.OverlayList.get(OverlayList.java:120)
	at
com.sas.analytics.risk.visuals.VariableGroupItem$VariableItemList.get(VariableGr
oupItem.java:198)
	at com.sas.analytics.cmp.util.JoinedList.get(JoinedList.java:159)
	at com.sas.analytics.cmp.util.JoinedList.indexOf(JoinedList.java:216)
	at
com.sas.analytics.risk.visuals.RiskItemTreeModel.getIndexOfChild(RiskItemTreeMod
el.java:174)
	at
com.sas.analytics.risk.visuals.RiskItemTreeModel.treeEventFromPropertyEvent(Risk
ItemTreeModel.java:296)
	at
com.sas.analytics.risk.visuals.RiskItemTreeModel.fireTreeNodesInserted(RiskItemT
reeModel.java:199)
	at
com.sas.analytics.risk.visuals.RiskItemTreeModel.processPropertyChange(RiskItemT
reeModel.java:183)
	at
com.sas.analytics.risk.visuals.RiskItemTreeModel$3.propertyChange(RiskItemTreeMo
del.java:100)
	at java.beans.PropertyChangeSupport.firePropertyChange(Unknown Source)
	at java.beans.PropertyChangeSupport.firePropertyChange(Unknown Source)
	at
com.sas.analytics.risk.visuals.RiskItem.firePropertyChange(RiskItem.java:248)
	at com.sas.analytics.risk.visuals.RiskItem.refresh(RiskItem.java:1075)
	at
com.sas.analytics.risk.visuals.VariableGroupItem.refresh(VariableGroupItem.java:
50)
	at com.sas.analytics.risk.visuals.RiskItem.refresh(RiskItem.java:1079)
	at
com.sas.analytics.risk.visuals.VariableDefinitionGroupItem$VariableTypeItem.refr
esh(VariableDefinitionGroupItem.java:71)
	at com.sas.analytics.risk.visuals.RiskItem.refresh(RiskItem.java:1079)
	at
com.sas.analytics.risk.visuals.VariableDefinitionGroupItem.refresh(VariableDefin
itionGroupItem.java:183)
	at
com.sas.analytics.risk.visuals.commands.VariableRenameCommand.doCommand(Variable
RenameCommand.java:58)
	at com.sas.analytics.risk.visuals.commands.Command.execute(Command.java:403)
	at
com.sas.analytics.risk.visuals.commands.CommandDispatcher$1.run(CommandDispatche
r.java:291)

Additionally, the system could become locked and need to be re-started. Changes that have not been saved might be lost.

The workarounds are as follows:

After an action such as creating a new variable or re-naming a variable, click the Refresh icon or use View → Refresh.

In the Configuration Tree, do not open any of the Variable Definitions, which will enable you to create multiple variables of the same type, but not to re-name them. Note that you can expand, collapse, and refresh the tree.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
Product Family	Product	System	Reported	Fixed*	Reported	Fixed*
SAS System	SAS Risk Dimensions Enterprise Edition	Microsoft Windows NT Workstation	5.2
		Microsoft Windows 2000 Professional	5.2
		Microsoft Windows 2000 Server	5.2
		Microsoft Windows 2000 Datacenter Server	5.2
		Microsoft Windows 2000 Advanced Server	5.2
		Microsoft Windows 95/98	5.2
		Microsoft® Windows® for x64	5.2	5.3		9.2 TS2M3
		Windows 7 Professional x64	5.2	5.3		9.2 TS2M3
		Windows 7 Professional 32 bit	5.2	5.3		9.2 TS2M3
		Windows 7 Home Premium x64	5.2	5.3		9.2 TS2M3
		Windows 7 Home Premium 32 bit	5.2	5.3		9.2 TS2M3
		Windows 7 Enterprise x64	5.2	5.3		9.2 TS2M3
		Windows 7 Enterprise 32 bit	5.2	5.3		9.2 TS2M3
		Microsoft Windows XP Professional	5.2	5.3		9.2 TS2M3
		Microsoft Windows Server 2008	5.2	5.3		9.2 TS2M3
		Microsoft Windows Server 2003 Standard Edition	5.2	5.3		9.2 TS2M3
		Microsoft Windows Server 2003 Enterprise Edition	5.2	5.3		9.2 TS2M3
		Microsoft Windows Server 2003 Datacenter Edition	5.2	5.3		9.2 TS2M3
		Windows 7 Ultimate 32 bit	5.2	5.3		9.2 TS2M3
		Windows 7 Ultimate x64	5.2	5.3		9.2 TS2M3
		Windows Millennium Edition (Me)	5.2
		Windows Vista	5.2	5.3		9.2 TS2M3
		64-bit Enabled AIX	5.2	5.3		9.2 TS2M3
		64-bit Enabled HP-UX	5.2	5.3		9.2 TS2M3
		64-bit Enabled Solaris	5.2	5.3		9.2 TS2M3
		HP-UX IPF	5.2	5.3		9.2 TS2M3
		Linux	5.2	5.3		9.2 TS2M3
		Linux for x64	5.2	5.3		9.2 TS2M3
		Solaris for x64	5.2	5.3		9.2 TS2M3

* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.

Type:	Problem Note
Priority:	alert

Date Modified:	2010-11-06 22:20:51
Date Created:	2010-01-27 09:39:52