Porting PL/pgSQL to PL/SQL.

I'm going to move database from Postgres to Oracle 10g. This DB has a lot of PL/pgSQL. I have found a several article/web-pages describing the opposite transition is there anyone on PL/pgSQL to PL/SQL?
Also there is something called PL/R for Postgres that lets you write PL in R programming language, is there anything similar for Oracle 10g? Or is there anyway to achieve the same in Oracle?
Message was edited by:
akalars

is there anything similar for Oracle 10g? you can write SQL and PL/SQL in host of languages, including but not limiting to, C/C++, java, cobol etc..
C:\>proc
Pro*C/C++: Release 10.1.0.2.0 - Production on Sun Jan 29 08:42:08 2006
Copyright (c) 1982, 2004, Oracle. All rights reserved.
C:\>procob
Pro*COBOL: Release 10.1.0.2.0 - Production on Sun Jan 29 08:42:12 2006
Copyright (c) 1982, 2004, Oracle. All rights reserved.

Similar Messages

Sql server 2012 express - tcp/ip connection to named instance using dynamic port not working

I have a named instance on a SQL 2012 Express server that won't connect via TCP/IP when wanting to connect off of the dynamic port. I can connect via shared memory locally on the server.   I can connect to the namespace when specifying the
dynamic port listed in the configuration manager.
This is the only named instance on the server and it is not the default.
TCP/IP is enabled
Allow Remote connections is enabled
the server browser service is running
I can connect via the dynamic port number
I am testing the connection locally on the server, so I don't believe a firewall is the issue. I get the same results if I test it from a remote computer.
When using the sqlcmd (sqlcmd -S tcp:SQLSRVR\NAMEINST -E) I get the message that "the requested protocol isn't supported [xfffffffff]".   The command (sqlcmd -S tcp:SQLSRVR\NAMEINST,59992 -E) works.
Through SSMS, I get the message "the connection was actively refused".
On other boxes, I can connect with the named instance without having to specify the port.
I have looked through the sql logs and nothing much shows up. The log does show that is listening on the port # for ipv4 and ipv6.   There is also a line in there talking about the SPN not being registered and not to worry about it if
you are not using Kerberos. I logged in through shared memory and it said I was using NTLM.
Any help would be appreciated.
thanks.

Hi clw,
I’m writing to follow up with you on this post. According to your description, I do a test, if you configure the database engine to listen on a specific TCP port (59992), and
the port is opened in the firewall. If you want to connect to the SQL Server instance, you 'd better to
use the port number.
In my opinion, by default, the default instance of the Database Engine uses port 1433, usually, if you have configured the server to listen on a non-default port number, when an instance of SQL Server uses dynamic port allocation, the connection string that
is built at the SQL Server client does not specify the destination TCP/IP port unless the user or the programmer explicitly specifies the port. Therefore, the SQL Server client library queries the server on UDP port 1434 to collect the information about the
destination instance of SQL Server.
If UDP port 1434 is disabled, the SQL Server client cannot dynamically determine the port of the named instance of SQL Server. Therefore, the SQL Server client may be unable to connect to the named instance of SQL Server. In this situation, the SQL Server
client must specify the dynamically allocated port where the named instance of SQL Server is listening.
For more information about configuring an instance of SQL Server to listen on a specific TCP port or dynamic port, you can review the following article.
https://support.transfrm.com/entries/503111-How-to-configure-an-instance-of-SQL-Server-to-listen-on-a-specific-TCP-port-or-dynamic-port
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support

Pre-Requisite Check SQL Server 2012 SP2 TCP Port Enabled Error

When doing the pre-requisite check to install SCCM (CAS) using an instance of SQL Server 2012 SP2, you get the following error even though SQL Server TCP port has been enabled, set to static port 4022 on the IP addresses in use in SQL Server Configuration
Manager under Protocols for <SQLInstanceName>: configuration manager primary site and central administration site require sql server tcp enables and set to static port
To resolve this issue, make sure "4022" is also set in the IPAll node in SQL Server Configuration Manager under Protocols for <SQLInstanceName> then restart the SQL Service and re-run the pre-requisite check and you should be good to go.
To avoid SCCM SQL-related install failure, keep in mind that SCCM SQL Service Broker (SSB) (used to replicate data between database sites) is set to port 4022 by default. This is different from and cannot be same as the tcp static port set in SQL Server
Configuration Manager under Protocols for <SQLInstanceName>. For example SSB can use its default tcp port 4022 while a static tcp port of 4023 can be set in SQL Server Configuration Manager under Protocols for <SQLInstanceName> or vice-versa. The
SCCM SSB port number can be adjusted during SCCM installation on the Database Information page. My take it so change SSB port to 4023 and leave SQL default port at 4022 since SQL serves potentially many apps while SSB is used within/by SCCM.
If you are getting errors relating to SQL Server service running accounts, SQL Server Collation, and/or SQL Server sysadmin rights while attempting to install a primary site, unselect the SCCM installation option to install default settings at the beginning
of the install process.
Also, ensure to install important updates and restart the server.

Thank you for sharing.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Firewall issue with centralized SQL server - port 52384

Hi,
I have dedicated, centralized MS SQL 2012 server for our internal infrastructure with few instances. There is dedicated named instance SC for SC Family Products running on TCP port 1435. Also Server Browser running on UDP 1434 is enabled. I'm trying to install
SCOM 2012 R2. I got to the step Configure the Operational Database and here, I encountered a problem. I try to connect to my SQL server and put into
Server name and instance name SQL\SC and into SQL Server port 1434 or 1435, it doesn't connect. If I turn off firewall on SQL server, it connects without problems. On SQL server, I already have allowed incoming communication on ports UDP 1434
and also TCP 1433-1436. Than, I found out, that I need to allow in TCP 135 so I did it. It didn't work. Than I allowed TCP 49154-49157 for reporting services - it still didn't work. Last thing I allowed (using Microsoft Network Monitor) was TCP port 52384
and suddenly, it worked .
I know what UDP 1434 and TCP 1433-1436 are for. Also, I understand why I have to open 135 and 49154-49157. But I am pretty confused by the port 52384 - what is it for ? Why it isn't mentioned in documentation ? I am pounding with this problem for a while,
and also, I found out, that my SC VMM is not working, if I do not allow all of these ports - so, probably not only used by SCOM ?
Can anyone explain what's that port for ? Or why it's not enough to open 1434, 1433-1436, 135 and 49154-49157 ?
Thanks
Tomas

Hi,
I didn't install SCOM yet. I am stuck at installation, till I figure out why port 52384 needs to be opened.
1. My SQL Server Configuration Manager is set like this:
Protocols for SC - TCP/IP Enabled
IP2
Active : Yes
Enabled : Yes
IP Address : ipv4 ip address of server
TCP Dynamic Ports : (blank)
TCP Port : 1435
So, that should be ok, right?
2. If I turn off firewall on SQL, everything connects ok - so based on that, I suppose that SCOM server firewall is configured ok . It's issue on SQL.
On SQL server, I have these inbound rules:
COM+ Network Access (DCOM-In) - TCP 135 enabled
HTTP/HTTPS - TCP 80,443 enabled
SCOM Reporting - TCP 49154-49157 enabled
SQL UDP ports - UDP 1433-1437 enabled
SQL TCP ports - TCP 1433-1435 enabled
SCOM 52384 - TCP 52384 enabled <- this is the port I don't understand, why it should be opened
If I disable any of these rules, my connection will not pass. I figured out those ports using Microsoft Network Monitor on SQL server.
3. Those databases do not exist yet. I am stuck at 3th step of Operations Manager Setup - at Configure the operational database.
There are fields Server name and instance name, SQL Server port, Database name, Database size, Data file folder, Log file folder
. First two are writable and the rest is greyed out. If I don't turn off firewall and I don't enable all rules from point 2 on SQL server and than put in the SQL server name with instance (SQL\SC) and port 1434 (or 1435) it gives
me red cross, and rest of the page stays greyed out - so, it's unable to connect. If I turn off firewall, or enable all the rules in previous point (2) I am able to change name of the database, database size, data/log file folder. But if I disable any
of those ports, it stays greyed out - I am concerned about port 52384, why it should be opened? What is it for? Why it isn't mentioned in any documentation? Or am I doing something wrong?
Thanks
Tomas

PL/SQL Local Debug restricting ports

Does anyone know how to restrict the ports used by the PL/SQL local debugger?

Shay,
It's not working that way for me. When I open up the PL/SQL function in the editor and then right click within the editor and choose debug, I'm presented with a dialog window titled "Debugger Host for Database Debugging".
This box has only one input control (IP address) and the following text:
"If JDeveloper is running on a machine in a VPN, enter the IP address of the machine as it is known to the rest of the VPN."
I've tried the default, "127.0.0.1", my IP address and even the IP address of the machine running the Oracle DB.
All three of these choices yield the following results:
=======================================================
Connecting to the database QF.
Executing PL/SQL: ALTER SESSION SET PLSQL_DEBUG=TRUE
Executing PL/SQL: ALTER SESSION SET PLSQL_COMPILER_FLAGS=INTERPRETED
Executing PL/SQL: CALL DBMS_DEBUG_JDWP.CONNECT_TCP( '10.69.35.11', '1544' )
ORA-30683: failure establishing connection to debugger
ORA-12541: TNS:no listener
ORA-06512: at "SYS.DBMS_DEBUG_JDWP", line 68
ORA-06512: at line 1
Process exited.
Disconnecting from the database QF.
=======================================================
Thanks,
Greg

How to Configure Remote Connections To SQL Server 2008 R2 Express

Post written June 10, 2010 and pertains to:
SQL Server 2008 R2 Express on both my server and local machines: SQLX_SRV,
SQLX_LOC
SQL Server 2008 R2 Management Studio on both my server and local machines:
MS_SRV, MS_LOC
Windows Server 2008 R2 Enterprise installed on a Hyper-V VPS: WS
SQL Server Configuration Manager on both my server and local machines:
CMGR_SRV, CMGR_LOC
Server Manager: SMGR
I am connecting to my hosting server via Remote Desktop Connection: RDC
I installed SQLX_SRV and MS_SRV on my hosting server and SQLX_LOC and MS_LOC on my local development machine. I am able to use MS_LOC to connect to SQLX_LOC and to use MS_SRV to connect to SQLX_SRV. However I am not able to use MS_LOC to connect
with SQLX_SRV. Here's what I have done so far:
SMGR -> Configuration -> Windows Firewall to turn off the Windows Firewall for Domain, Private and Public profiles. Obviously I'll change this later, but until I can connect I want to remove as many variables as possible.
CMGR_SRV -> SQL Server Services to confirm that both SQL Server (SQLEXPRESS) and SQL Server Browser services were running.
CMGR_SRV -> SQL Server Network Configuration -> Protocols for SQLEXPRESS to ENABLE the Shared Memory, Named Pipes, and TCP/IP protocols and DISABLE the deprecated VIA protocol.
CMGR_SRV -> SQL Server Network Configuration -> Protocols for SQLEXPRESS -> double click TCP/IP to open the TCP/IP properties dialogue. On the Protocol tab Enabled: Yes, Keep Alive: 30000, changed Listen All to No. I've tried it both
ways, but I've got six IP addresses on my server and I wanted to configure SQLEXPRESS to listen to only the first and primary IP. On the IP Addresses tab went to IPALL and cleared the TCP Dynamic Ports field and entered 1433 in the TCP Port field.
For my first and primary IP Address I made sure that Enabled was Yes, I cleared the TCP Dynamic Ports field, and entered 1433 in the TCP Port field. For all other IP Addresses Enabled was set to No and I cleared both the TCP Dynamic Ports and TCP Port
fields.
CMGR_SRV -> SQL Server Services -> SQL Server (SQLEXPRESS) right click and Restart. This of course stopped and restarted my instance of SQLX_SRV enabling the TCP/IP configuration in the previous step to take effect.
On my server, SQLX_SRV is the only instance of SQL Server running and so it's easy to hard wire it to the default port 1433.
The instance name for both SQLX_SRV and SQLX_LOC is the default "SQLEXPRESS". My server machine name is "SERVER1" on the EnglishBrains.com domain. So the proper local name (local within the context of my remote server as connected via RDC) for
my instance of SQLX_SRV would be:
SERVER1\SQLEXPRESS
Note the use of a backslash NOT a forward slash.
Of course to connect remotely from my development machine, which is not on the same domain as my hosting server, I would need to specify the domain as well, so the SQL Server name becomes:
SERVER1.EnglishBrains.com\SQLEXPRESS
I must also use SQL Server Authentication. Before I can use such a remote connection, however, there are still several configuration steps required. So on my server (connected via RDC) I used MS_SRV to connect to SQLX_SRV using SERVER1\SQLEXPRESS
for the server name and Windows Authentication. Once connected I performed the following steps:
MS_SRV -> right click the connected parent SERVER1\SQLEXPRESS instance node at the top -> Properties -> Security -> Server authentication: select "SQL Server and Windows Authentication mode". This will enable connections using either type
of authentication.
Next, leaving the Server Properties dialogue open, Connections -> check "Allow remote connections to this server" box.
Click OK to save these changes and close the Server Properties dialogue.
MS_SRV -> Security -> right click Logins and select "New Login...", the Login - New dialogue opens.
On the General page Enter a name for your new login
Select SQL Server Authorization
Enter and confirm a password
Uncheck Enforce password expiration
Select the default Database and Language
On the ServerRoles page Public will be checked, also check SysAdmin. This is probably not a good idea and I'll uncheck this as soon as I can connect to the SQLX_SRV.
On the User Mapping page select the databases you want your new Login to access and enter the Default Schema of "dbo".
At the bottom of the User Mapping page you'll see the Database Roles table. Public will be selected by default. Also select db_Owner. Again this is probably not a good idea, and I'll refine this once I can connect.
On the Status page confirm that "Grant" is checked under "Permission to connect to database engine" and "Enable" is checked under "Login".
Click OK to save all changes and close the Login - New dialogue.
With these steps completed you should now be able to use MS_SRV to connect to SQLX_SRV using SQL Server Authentication by supplying the name and password for your new Login. I tried this and it worked fine. Next I tried to use this same login
remotely, that is I went to my local development machine and used MS_LOC to try and connect to SQLX_SRV by using
SERVER1.EnglishBrains.com\SQLEXPRESS
and opting for SQL Server Authentication and supplying the name and password of my new login.
THIS DID NOT WORK?? Instead I get the following error message:
Cannot connect to SERVER1.EnglishBrains.com\SQLEXPRESS.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider:
SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
For help, click:
http://www.microsoft.com/products/ee/transform.aspx?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1
If you follow the suggested help link, you are told:
The SQL Server client cannot connect to the server. This error could be caused by one of the following reasons:
A specified SQL Server instance name is not valid.
The TCP, or named pipes protocols are not enabled.
The firewall on the server has refused the connection.
The SQL Server Browser service (sqlbrowser) is not started.
WRONG on all 4 counts! The instance name IS valid. Both TCP/IP and Named Pipes protocols are enabled. The firewall has been shut down, so it is not relevant. Finally the SQL Server Browser IS started.
The next thing I tried was to circumvent discovery by the SQL Browser service by using the following syntax to specify the IP address and port directly when specifying the SQL Server name.
tcp:68.71.134.186,1433
Using this in the Server Name field I was able to use MS_SRV to successfully connect to SQLX_SRV (using SQL Server Authentication of course) with or without the SQL Browser service running.
However when I tried to connect from MS_LOC to SQLX_SRV using this same login (WITH SQL Browser service running just for good measure) it does not work?? I get the following error message:
Cannot connect to tcp:68.71.134.186,1433.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider:
TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) (Microsoft SQL Server, Error: 10060)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=10060&LinkId=20476
If you follow the help link you are told:
"The SQL Server client cannot connect to the server. This error could occur because either the firewall on the server has refused the connection or the server is not configured to accept remote connections."
However, the firewall has been shut down and the server HAS been configured to accept remote connections!
I confirmed that i could indeed Ping to 68.71.134.186 and running NetStat -a |find /i "listening" on the server shows that the server is indeed listening at 68.71.134.186 Port 1433 -- which is why I was able to connect to SQLX_SRV using MS_SRV with
tcp:68.71.134.186,1433 .
IN SUMMARY: Even though I can connect to my SQLEXPRESS instance multiple ways from the server itself, I cannot connect remotely from my development machine!
If anyone can help me figure out why I would be very, very grateful!

My two cents to help you out on c# code example to configure the remote sql server express.
Hope it helps. It works, but you have to be extra carefull to read it all and setup the server configuration and netsh commands; also the port fowarding on the router.
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Data.SqlClient;
namespace sqlremoteconnection
class Program
static void Main(string[] args)
// this is the local sql server connection
// 192.168.1.101\SQLEXPRESS
// now, the configuration for remote access:
// activate SQL SERVER BROWSER - set it to start "automatic"; then START UP
// SQL Server Configuration Manager
// --> SQL SERVER BROWSER -> properties -> Service -> Start Mode -> automatic -> apply
// --> Log On -> Start -> Ok
            // netsh firewall set portopening protocol = TCP port = 1433 name = SQLPort mode = ENABLE scope = all profile = CURRENT
            // netsh firewall set portopening protocol = UDP port = 1434 name = SQLPort mode = ENABLE scope = all profile = CURRENT
            // netsh advfirewall firewall add rule name = SQLPort dir = in protocol = tcp action = allow localport = 1433 remoteip = any profile = PUBLIC
            // netsh advfirewall firewall add rule name = SQLPort dir = in protocol = udp action = allow localport = 1434 remoteip = any profile = PUBLIC
// VERY IMPORTANT FOR REMOTE ACCESS: you have to add the rules on port fowarding
// on the router!!!
// TCP: 1433
// UDP: 1434
// or just a personal port like TCP 31433/UDP 31434
// read carefully the netsh commands above
// server name: 123.132.24.177\SQLEXPRESS
// server name: anyurl.myftp.org\SQLEXPRESS,1433 <<-- regular port
// server name: anyurl.myftp.org\SQLEXPRESS
// server name: anyurl.myftp.org\SQLEXPRESS,31433 <<-- WOW different PORT here!!!
SqlConnection myConnection = new SqlConnection(
"user id=sa;" +
"password=password_goes_here!;" +
"server=anyurl.myftp.org\\SQLEXPRESS,31433;" +
//"Trusted_Connection=no;" +
"database=database_name_here; " +
"connection timeout=30");
try
myConnection.Open();
catch (Exception e)
Console.WriteLine(e.ToString());
try
SqlDataReader myReader = null;
SqlCommand myCommand = new SqlCommand("select * from mytable", myConnection);
myReader = myCommand.ExecuteReader();
while (myReader.Read())
Console.WriteLine(myReader["tab01_name"].ToString());
Console.WriteLine(myReader["tab01_age"].ToString());
catch (Exception e)
Console.WriteLine(e.ToString());
try
myConnection.Close();
catch (Exception e)
Console.WriteLine(e.ToString());
Adelino Araujo

[Forum FAQ] How to tell if the DAC port is automatically changed or not

Introduction
Per Books Online:
http://msdn.microsoft.com/en-us/library/ms189595.aspx
SQL Server listens for the DAC on TCP port 1434 if available or a TCP port dynamically assigned upon Database Engine startup.
Also, we can go to the following registry to specify the DAC port number manually:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQLServer\SuperSocketNetLib\AdminConnection\Tcp
The error log contains the port number the DAC is listening on. Besides looking at the error log, how to find which port is used by DAC connection and how to tell if the DAC port is manually set by us or assigned automatically by SQL Server?
Solution
The following query can be used to check if there is an existing DAC connection and it also give us the port number used by dedicated admin connection.
SELECT name,local_tcp_port FROM sys.dm_exec_connections ec
join sys.endpoints e
on (ec.endpoint_id=e.endpoint_id)
WHERE e.name='Dedicated Admin Connection'
Here is the scenario to test if the DAC port is automatically changed or not.
There are two instances are running on one server. I specified the same DAC port number 5555 for the two SQL Server instances by modifying the registry
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQLServer\SuperSocketNetLib\AdminConnection\Tcp
Opened the DAC connection to instance 1. Executed the above query, it returns the result:
name
local_tcp_port
Dedicated Admin Connection 5555
Then, opened a DAC connection to instance 2. It throw out the following error message:
Sqlcmd: Error: Microsoft SQL Server Native Client 11.0 : Client unable to establish connection because an error was encountered during handshakes before login.
Common causes include client attempting to connect to an unsupported version of SQL Server, server too busy to accept new connections or a resource limitation (memory or maximum allowed connections) on the server..
Sqlcmd: Error: Microsoft SQL Server Native Client 11.0 : TCP Provider: An established connection was aborted by the software in your host machine..
Sqlcmd: Error: Microsoft SQL Server Native Client 11.0 : Client unable to establish connection.
Sqlcmd: Error: Microsoft SQL Server Native Client 11.0 : Client unable to establish connection due to prelogin failure.
The above error message was thrown out because the DAC port number 5555 was not available for instance 2 which was occupying by instance 1. After restarting the SQL Server engine service of instance 2, if checking in the registry, you would see a new DAC port
number has been assigned to the second instance.
Then, the DAC connection to instance 2 succeed this time and executed the above query, it returned the same port number which is same as the one in the registry key and the port number was assigned automatically.
DAC port will not change even SQL Server service is restarted only if the TCP port is available.
More Information
http://msdn.microsoft.com/en-us/library/ms189595.aspx
Applies to
SQL Server 2012
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

I tested your script after
establishing a DAC connection from SSMS 2014. It worked as described. Thank you.
SELECT name,local_tcp_port FROM sys.dm_exec_connections ec
join sys.endpoints e
on (ec.endpoint_id=e.endpoint_id)
WHERE e.name='Dedicated Admin Connection'
name local_tcp_port
Dedicated Admin Connection 1434
Kalman Toth Database & OLAP Architect
SQL Server 2014 Design & Programming
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

Install multiple version of SQL Server on a same machine, both with default instance?

We have an almost idle server (windows server 2008 R2) with SQL Server 2008 Enterprise with default instance. We would like to port all the data, install SQL Server 2012 developer edition and use it as testing server. Is that possible we still choose default
instance name on 2012 developer version? Do we have to shutdown or uninstall the 08 Enterprise? If we keep both versions running, does SQL server 2012 have to choose a named instance? Any suggestion would be appreciated.

There can only be a single default instance and multiple named instances.
BOL: http://technet.microsoft.com/en-us/library/ms143547.aspx
Kalman Toth Database & OLAP Architect
SELECT Video Tutorials 4 Hours
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

Upgrade from 2005 express to 2008 r2 express - provisionsystemaccounts.sql error

Hi,
I’ve been upgrading several of my clients and ran into this problem for one of them.
When doing the upgrade I got..
Looking at the error logs indicated..
2015-03-21 11:54:07.58 spid7s
Database 'master' is upgrading script 'provisionsystemaccounts.sql' from level 0 to level 2.
2015-03-21 11:54:07.59 spid7s
2015-03-21 11:54:07.59 spid7s
Starting provisionsystemaccounts.sql ...
2015-03-21 11:54:07.59 spid7s
2015-03-21 11:54:08.02 spid7s
Error: 15151, Severity: 16, State: 1.
2015-03-21 11:54:08.02 spid7s
Cannot find the user 'FILESERVER01\SQLServer2005MSFTEUser$FILESERVER02$ORSQLEXP', because it does not exist or you do not have permission.
2015-03-21 11:54:08.03 spid7s
Error: 912, Severity: 21, State: 2.
2015-03-21 11:54:08.03 spid7s
Script level upgrade for database 'master' failed because upgrade step 'provisionsystemaccounts.sql' encountered error 15151, state 1, severity 16. This is a serious error condition which might interfere with regular operation and the database will be
taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database
so that the script upgrade steps run to completion.
2015-03-21 11:54:08.03 spid7s
Error: 3417, Severity: 21, State: 3.
2015-03-21 11:54:08.03 spid7s      Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how
to rebuild the master database, see SQL Server Books Online.
2015-03-21 11:54:08.03 spid7s
  SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.Running the Repair from the Installation centre
brings up the same error.
I noticed that the instance appears to be upgraded but basically the service won’t run. I can start it but it just stops again.
So I found this which seems the same as my problem..
https://ilkirk.wordpress.com/2011/03/07/in-place-sql-upgrade-error-2005-to-2008/
Even though I can start the SQL Services using point 1 from the link above I can’t connect to sql using DAC.
The sqlcmd won’t work and trying to connect through SSMS.
> SQLCMD –E –A. I’ve also tried >SQLCMD FILESERVER1\ORSQLEXP –E –A and get the same results
HResult 0xFFFFFFFF, Level 16, State 1
SQL Server Network Interfaces: An error occurred while obtaining the dedicated administrator connection (DAC) port.
Make sure that SQL Browser is running, or check the error log for the port number [xFFFFFFFF].
When I try to connect to DAC via SSMS I get ..
So I seem to currently have 2 problems, one using sqlcmd/DAC and the other with provisionsystemaccounts.sql.
The sqlbrowser is running but from 90 (not sure if that matters) and I have removed (following online research) the 80 and 90 binn settings from the PATH just leaving 100 but this hasn’t changed the errors.
I’ve tried enabling DAC using this advice below but it hasn’t made any difference. The service keeps stopping and no SQLCMD action.
http://www.mssqltips.com/sqlservertip/2538/enabling-dedicated-administrator-connection-in-sql-server-2008-express-edition/
So after trying numerous options I currently stumped.

An update to this. I can now DAC via sqlcmd.
Following the advice on
[url]https://ilkirk.wordpress.com/2011/03/07/in-place-sql-upgrade-error-2005-to-2008/[/url]
I'm at point 3
3.Issue a ‘create login’ command to create the user / group you’re missing, followed by the all important GO
and I'm a bit unclear on what to do. The user according to the error log is 'FILESERVER01\SQLServer2005MSFTEUser$FILESERVER02$ORSQLEXP'
and I tried
>sp_addsrvrolemember 'FILESERVER01\SQLServer2005MSFTEUser$FILESERVER02$ORSQLEXP', 'sysadmin'
>go
adding this seemed to work without error but running the repair from the installation centre bought up the exact same error as before.
So, bearing in mind using the advice from the above link
Have I added the user to the correct group?
If not how do I do that?
In the advice he also mentions..
Now – why did this happen? Well, in my situation it seems to be related to the fact that I upgraded the default instance first which also upgraded the Full Text Engine. That, in turn, removed the Full Text Engine user group from the local groups.
In particular, I was missing “<ServerName>\SQLServer2005MSFTEUser$<ServerName>$MSSQLSERVER”. Note the fact that it mentions the default instance, not the named instance!
The SQLServer2005MSFTEUser login refers to a local Windows group that is used for controlling access to the Full Text Engine. I suspect that when I upgraded the default instance, the installer removed the group from Windows, but not necessarily
from the named instance of SQL. Once I recreated the group, granted my service account access to mirror the other similar groups, and added that login back into SQL via the DAC, everything went fine from there.
thanks,

500 Internal Server Error - java.sql.SQLException: Invalid column index

500 Internal Server Error
java.sql.SQLException: Invalid column index     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:137)     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:174)     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:239)     at oracle.jdbc.driver.OracleResultSetImpl.getObject(OracleResultSetImpl.java:851)     at com.stardeveloper.servlets.db.InsertServlet.doPost(InsertServlet.java:88)     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)     at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)     at oracle.security.jazn.oc4j.JAZNFilter.doFilter(Unknown Source)     at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:663)     at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)     at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)     at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpRequestHandler.run(HttpRequestHandler.java:285)     at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpRequestHandler.run(HttpRequestHandler.java:126)     at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)     at java.lang.Thread.run(Thread.java:534)
This is the connection part of the java code
     // connecting to database
          Connection con = null;
          Statement stmt = null;
          ResultSet rs = null;
          PreparedStatement ps = null;
          try {
               Class.forName("oracle.jdbc.driver.OracleDriver");
          con=DriverManager.getConnection("host:port:sid, userName, password");
               String sql;
          sql = "INSERT INTO USERSS(user_id, username) VALUES (?,?)";
               ps = con.prepareStatement(sql);
               stmt = con.createStatement();
               // inserting records
               if(proceed) {
                    ps.setString(1, user_id);
                    ps.setString(2, username);
                    ps.executeUpdate();
desc userss;
Name Null? Type
USER_ID NOT NULL NUMBER(5)
USERNAME VARCHAR2(15)
Index_Name table_name
USERSS_PK1 USERSS
when I try to insert values, it is inserting, but at the end I am getting the above error. I am using JDeveloper 10g and database [Oracle9i Enterprise Edition Release 9.2.0.7.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.7.0 - Production]

I suggest you should alter the JDBC Driver and select one for Oracle 9i.
Which version is your JDev10g?

JDBC Ipv6 address, what is the port number?

I believe there might an ambiguity when using IPv6 IP address
format with JDBC connection address.
A common format for the connection url is:
jdbc:subprotocol:subname
Where:
subprotocol = <some name>
subname = //<{IP Address|Machine Name}[:port]>/<database name>
Example:
jdbc:sql:t9://130.168.200.30:1433/database1
An IPv6 has the format
x:x:x:x:x:x:x:x
where the 'x's are the hexadecimal values of the
eight 16-bit pieces of the address. This is the
full form. For example,
1:2:0:0:5:6
The IPv6 format also allows an abbreviation version where 0's are
replaced with "::". So, the above address could also be written
as:
1:2::5:6
An optional port number can be added. For example,
1:2:0:0:5:6:8888
or as the following if using the abbreviation version of IPv6
1:2::5:6:8888
While decoding this version of the address, an ambiguity arises.
Does the address expand to
1:2:0:5:6:8888 // no optional port number
or
1:2:0:0:5:6:8888 // contains the optional port number.
Is this correct? If so, how are vendors dealing with this?
Thanks,
.........Ken

>
1:2:0:5:6:8888 // no optional port optional port numberYou are claiming that this is a valid address?
>
Is this correct? I am rather certain that you can not create a form that is ambiguous. Ipv4 has either 4 or 5 integers. Where Ipv6 has either 6 or 7.
If so, how are vendors dealing with
this?Realistically the following situations probably exist
- They are not dealing with it.
- The use the functionality in java.net.* and it deals with it.
- They wrote their own stuff which mimics what java.net.* does.

BT2010 Installed Cum Update Packs for Adapters and getting run-time errors with WCF-SQL

The process has been working fine for months. Then we installed Cum Update packs to BT2010 (I'll get the exact C.U.'s from our admin guy) and last night got probably 20 errors similar to below.
   - Installed CU6 for BT2010
   - Installed CU3 for LOB (Adapters)
The SQL stored proc returns a mix of strings, integers, Guids, and dates; the BizTalk schema looks like matches perfectly. The stored proc runs fine in SSMS.
Got two errors for each, 1 in XLANG/s for the orchestration, and 1 for the Send port that calls the WCF-SQL adapter from the orchestration, and also 1 warning.
NOTE: This orchestration runs every 15 minutes 24x7. It calls the Stored Proc to find out which extracts it needs to create. Most all the extracts run at night. So if I run the stored proc during the day, it normally returns an empty result
set. Yet, the error below is happening every 15 minutes, even when the result set is empty. How can it generate a data conversion error when there is no data to be converted?
ORCHESTRATION/XLANG ERROR:
xlang/s engine event log entry: Uncaught exception (see the 'inner exception' below) has suspended an instance of service 'Common.Extract.Orchestrations.EFSRExtractHandler(2b35190e-5f11-e360-9ae8-daaf0372cbc3)'.
The service instance will remain suspended until administratively resumed or terminated.
If resumed the instance will continue from its last persisted state and may re-throw the same unexpected exception.
InstanceId: dc354922-73ef-46fc-ac3d-dbf793e5aaf8
Shape name:
ShapeId:
Exception thrown from: segment -1, progress -1
Inner exception: An error occurred while processing the message, refer to the details section for more information
Message ID: {066027B8-4750-4D63-A746-1390E9959E49}
Instance ID: {5A978538-5DD7-40D1-8826-D0486D129F84}
Error Description: System.InvalidCastException: Failed to convert parameter value from a String to a Guid. ---> System.InvalidCastException: Invalid cast from 'System.String' to 'System.Guid'.
   at System.Convert.DefaultToType(IConvertible value, Type targetType, IFormatProvider provider)
   at System.Convert.ChangeType(Object value, Type conversionType, IFormatProvider provider)
   at System.Data.SqlClient.SqlParameter.CoerceValue(Object value, MetaType destinationType, Boolean& coercedToDataFeed, Boolean& typeChanged, Boolean allowStreaming)
   --- End of inner exception stack trace ---
Server stack trace:
   at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.EndRequest(IAsyncResult result)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at System.ServiceModel.Channels.IRequestChannel.EndRequest(IAsyncResult result)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2.RequestCallback(IAsyncResult result)
Exception type: XlangSoapException
Source: Microsoft.XLANGs.BizTalk.Engine
Target Site: Void VerifyTransport(Microsoft.XLANGs.Core.Envelope, Int32, Microsoft.XLANGs.Core.Context)
The following is a stack trace that identifies the location where the exception occured
   at Microsoft.BizTalk.XLANGs.BTXEngine.BTXPortBase.VerifyTransport(Envelope env, Int32 operationId, Context ctx)
   at Microsoft.XLANGs.Core.Subscription.Receive(Segment s, Context ctx, Envelope& env, Boolean topOnly)
   at Microsoft.XLANGs.Core.PortBase.GetMessageIdForSubscription(Subscription subscription, Segment currentSegment, Context cxt, Envelope& env, CachedObject location)
   at Common.Extract.Orchestrations.EFSRExtractHandler.segment1(StopConditions stopOn)
   at Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s, StopConditions stopCond, Exception& exp)
SEND PORT ERROR:
A message sent to adapter "WCF-Custom" on send port "Send_SQL_Orch_Call_GetAirportsForExtract" with URI "mssql://QADBAlias.datacenter.local//QTAviation?" is suspended.
Error details: System.InvalidCastException: Failed to convert parameter value from a String to a Guid. ---> System.InvalidCastException: Invalid cast from 'System.String' to 'System.Guid'.
   at System.Convert.DefaultToType(IConvertible value, Type targetType, IFormatProvider provider)
   at System.Convert.ChangeType(Object value, Type conversionType, IFormatProvider provider)
   at System.Data.SqlClient.SqlParameter.CoerceValue(Object value, MetaType destinationType, Boolean& coercedToDataFeed, Boolean& typeChanged, Boolean allowStreaming)
   --- End of inner exception stack trace ---
Server stack trace:
   at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.EndRequest(IAsyncResult result)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at System.ServiceModel.Channels.IRequestChannel.EndRequest(IAsyncResult result)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2.RequestCallback(IAsyncResult result)
MessageId: {C1FB3913-42EB-4957-9289-16D03B02674E}
InstanceID: {46C9D190-902F-48CE-86CF-D8C3C5B8944D}

Hi,
About the error System.InvalidCastException: Failed to convert parameter value from a String to a Guid
, maybe the field on the database is varchar(string type).
And you can refer to the similar discussion:
http://stackoverflow.com/questions/12816641/failed-to-convert-parameter-value-from-string-to-guid
Hope it can help you.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Question on not being able to update SQL Server

Hi Gurus,
The following code is working OK to insert a Date/Time format data on MS Access.
I ported the database over to SQL Server with the same DateTime type of data in SQL Server. Could anybody think of a reason why this could not work and a possible solution.
I am setting the parameters for a SQL query to update the database, and the 17th parameter is the datetime field in SQL Server.
int cc = -1;
stmt.setDate(17, new java.sql.Date(k.getExpirationDate().getTime()));
cc = stmt.executeUpdate();
My email is [email protected] I appreciate your help.
Thanks
Venkat

Thanks. I am trying that way, but have not been successful before now or till now.
Thanks for your suggestion.
Venkat

WHY WE NEED TO ADD PORT NUMBER 1433 TO TCP/IP PROTOCOL INSTEAD OF UDP PROTOCOL

HELLO EVERYONE,
WHILE INSTALLING SQL SERVER I HAD ENCOUNTERED A WARNING MESSAGE REGARDING WINDOWS FIREWALL. AFTER SOME RESEARCH , I GOT TO KNOW THE STEPS TO TROUBLE SHOOT. IT SAYS I NEED TO GO TO WINDOWS FIREWALL AND ADD THE PORT NUMBER 1433 IN INBOUND & OUTBOUND
SECTION USING THE PROTOCOL- TCP/IP & 1434 TO INBOUND & OUTBOUND OPTION SECTION USING THE PROTOCOL OPTION - UDP.
I WANT TO KNOW CAN I ADD THE PORT NUMBER 1433 USING UDP PROTOCOL INSTEAD OF TCP/IP PROTOCOL IN FIREWALL SETTINGS ; IF NO THEN WHAT IS THE REASON?
AND WHY CANT WE HAVE USE ONE PROTOCOL : TCP OR UPD AND ADD THE PORT NUMBERS 1433 & 1434 FOR ACCESSING SERVER & SQL BROWSER SERVICES ?
PLEASE HELP.
THANKS , SAURAV GHOSH
saurav ghosh

We need to understand how the firewall setups are done in your environment like might be some restriction is there also need to check if IP level access are there for you or you need to get that.
Usually in secured setup, for your application, you need to get access on IP and Port to access database server. This is good also but may be more restriction you can bring in.
Also to update in inbound and outbound, is required too at times when you have firewall services on as this is being disabled\stop too in many setup due to application level functionality issues too.
You can definitely go ahead and add these ports, this will not disturb you environment as you are just giving access to sql server available on host which is accessed, how? you need to check, may be your application is accessing through IP not name, application
will look for Port on this IP.
Check some details about it:
http://www.bleepingcomputer.com/tutorials/tcp-and-udp-ports-explained/
Also:
TCP 1433
TCP port 1433 is the default port for SQL Server. This port is also the official Internet Assigned Number Authority (IANA) socket number for SQL Server. Client systems use TCP 1433 to connect to the database engine; SQL Server Management Studio (SSMS) uses
the port to manage SQL Server instances across the network. You can reconfigure SQL Server to listen on a different port, but 1433 is by far the most common implementation.
UDP 1434
UDP port 1434 is used for SQL Server named instances. The SQL Server Browser service listens on this port for incoming connections to a named instance. The service then responds to the client with the TCP port number for the requested named instance.
The SQL Server Browser service listens for incoming connections to a named instance and provides the client the TCP port number that corresponds to that named instance. Normally the SQL Server Browser service is started whenever named instances of the Database
Engine are used. The SQL Server Browser service does not have to be started if the client is configured to connect to the specific port of the named instance.
Understanding this requirement:
http://support.microsoft.com/kb/287932/en-us
Good link: http://msdn.microsoft.com/en-in/library/cc646023.aspx
Hope this helps.
Santosh Singh

SP1 to R2 Upgrade - The installed Version of SQL Server is not supported for the operational database

Hello,
Am trying to upgrade a SCOM SP1 environment to SCOM R2( 3 MGT servers, 1 GW and 2 Web console boxes )
The prerequisites are failing and it is stating the following ;
Operational Database SQL Version Check - The installed Version of SQL Server is not supported for the operational database
Data Warehouse SQL Version Check - The installed Version of SQL Server is not supported for the data warehouse
The SQL servers are running SQL 2012 SP1 64 Enterprise, which is compatible.
All other pre-upgrade tasks have been done.
Help appreciated!

I'm having the exact same issue, I believe. I think that Tubble has problem with SCOM 2012. Not 2007.
I've checked the compatibility list for both SCOM 2012 SP1 and R2. All newer Windows Server and SQL versions are supported. We're running the SQL 2012 SP1 x64 Standard edition on a Windows Server 2012 Standard.
I even tried to move the database from SQL 2012 to an older SQL 2008 R2, but that's not supported either. Only upgrading. Not downgrading.
So, I started checking the opsMgrSetupWizard.log file for clues. And the error message was there as well. But the reason why it says not supported is that it can't get the info about the OS version, so I guess it assumes the OS version is to low. The RPC
service can not be reached.
[10:29:11]: Error: :GetRemoteOSVersion(): Threw Exception.Type: System.Runtime.InteropServices.COMException, Exception Error Code: 0x800706BA, Exception.Message: The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
[10:29:11]: Error: :StackTrace: at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.Management.ManagementScope.InitializeGuts(Object o)
at System.Management.ManagementScope.Initialize()
at System.Management.ManagementObjectSearcher.Initialize()
at System.Management.ManagementObjectSearcher.Get()
at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SetupValidationHelpers.GetRemoteOSVersion(String remoteComputer)
[10:29:11]: Debug: :IsSQLOnAValidComputer: remote OS version string was null or empty.
[10:29:11]: Error: :Error:IsValidSQLVersionCheck: SqlServer OS version is too low.
[10:29:11]: Debug: :**************************************************
[10:29:11]: Error: :<![CDATA[CheckPrerequisites: Logic Type:and IsValidOMDBSQLVersionCheck: 2]]>
[10:29:11]: Error: :
[10:29:11]: Error: :CheckPrerequisites: OMDBSqlVersionCheckTitle: Failed
[10:29:11]: Error: :
[10:29:11]: Debug: :**************************************************
[10:29:33]: Error: :GetRemoteOSVersion(): Threw Exception.Type: System.Runtime.InteropServices.COMException, Exception Error Code: 0x800706BA, Exception.Message: The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
[10:29:33]: Error: :StackTrace: at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.Management.ManagementScope.InitializeGuts(Object o)
at System.Management.ManagementScope.Initialize()
at System.Management.ManagementObjectSearcher.Initialize()
at System.Management.ManagementObjectSearcher.Get()
at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SetupValidationHelpers.GetRemoteOSVersion(String remoteComputer)
[10:29:33]: Debug: :IsSQLOnAValidComputer: remote OS version string was null or empty.
[10:29:33]: Error: :Error:IsValidSQLVersionCheck: SqlServer OS version is too low.
[10:29:33]: Debug: :**************************************************
So, in our case this was just a FW that was blocking some high ports between management server and SQL. I believe TCP port 135 also needs to be open.
Let's hope this fixes your issue as well, Tubble.
Have a great day!

Porting PL/pgSQL to PL/SQL.

Similar Messages

Maybe you are looking for