RE: [sqr-users] RE: PS SQR insert dilemma

[bpelton@communitymedical.org]

This might be way off subject, so forgive me...

It seems odd to me that developers would not have the ability to view code
that is in production, so I want to ask what kinds of "norms" there are out
there.  We have a small PeopleSoft shop with two developers, one dba and
one business analyst.  The developers have R/O access to the production
file server and full access to the development file servers.  The
developers are given the SYSADM password for the development databases and
have been given an Oracle user with select access for production (although,
this never seems to work because I'm constantly getting "table does not
exist" errors.)

I'm curious how much room, or how little, developers are given at other
sites.  Up until a few months ago, developers had the SYSADM password to
our production database so they could develop SQRs against live data (it
takes 14 hours! to refresh one of our development instances, ugh)  It was a
big source of frustration on my part when this was taken away because now
any SQL that needs to be run against production has to go through the DBA.
Also, we have a host of SQRs that were written without being setup to run
via a panel in PeopleSoft.  This also has to go through him.  The kicker
is, this makes almost no sense as the DBA wouldn't have a clue whether the
SQL or SQR that a developer wrote does any damage or not.  All our DBA is
responsible for is backups and refreshes.

How is it working at other sites??  If this is way off-topic, please feel
free to email me directly at bpelton@communitymedical.org

Brian Pelton
System Analyst
Community Medical Centers







"Knapp, Richard" <KnappR@umsystem.edu>@sqrug.org on 12/20/2002 06:59:44 AM

Please respond to sqr-users@sqrug.org

Sent by:    sqr-users-admin@sqrug.org


To:    <sqr-users@sqrug.org>
cc:    "Hegeman, Mary" <HegemanM@umsystem.edu>
Subject:    RE: [sqr-users] RE: PS SQR insert dilemma


Hi Denise,

I bet you are right.  That would explain all the facts in the case.  We
have a setup here where the developers cannot see the code that is in
production so we have to assume that the code in our dev directory is what
is on the server.  But this is not always the case.  What confirms your
theory for me is two things:  Les ran the code at his shop in Kentucky and
it worked - and the returned error message does not list the fields in the
first half of the insert statement which is what the code looked like for
the old version but not the new which does list all 96 field names.

I'm on my way over to a two tier machine to test this.

I knew it would be something embarrassing.  Sorry to trouble you all.

Richard Knapp
Database Programmer/Analyst
Institutional Research and Planning
University of Missouri System
573-882-8856
knappr@umsystem.edu


-----Original Message-----
From: dewhite@vicr.com [mailto:dewhite@vicr.com]
Sent: Friday, December 20, 2002 8:11 AM
To: sqr-users@sqrug.org
Subject: [sqr-users] RE: PS SQR insert dilemma


Hi Richard,

Grasping at straws here, but ... is there any possibility you are running
the
job on the server, and the new version of the SQR was not copied over to
the
server?

If not, maybe if you show us not only the error message, but the actual
code you
have in the SQR (the BEGIN-SQL paragraph), someone might come up with an
idea
(if you want to put ellipsis in place of all those zeros to save space in
the
message, that would be ok - it doesn't sound like the problem is with
them).

I remember some years back there were some problems when PeopleSoft was
trying
to switch from NAISC (if that's the right acronym) to SIC or vice versa,
and did
not coordinate everywhere it appeared.  But that was at least four years
ago,
and I don't remember specifically what the problems were.  I think they
changed
the fieldname in some places but not in others.

Denise White
Sr. Software Engineer
Vicor
--__--__--

Message: 2
Date: Thu, 19 Dec 2002 12:25:08 -0600
From: "Knapp, Richard" <KnappR@umsystem.edu>
To: <sqr-users@sqrug.org>
Subject: [sqr-users] PS SQR insert dilemma
Reply-To: sqr-users@sqrug.org


Hello Friends,

I am trying to resolve a strange error appearing when the patched version
of the
delivered PeopleSoft VETS100 report is run.  The error tells me there are
not
enough values on an insert to the temp table.  A check of the table
structure
against the structure described in the insert yields no differences.  A
count of
the values in the SQR insert statement is the same as the number of fields
in
the table _BUT_ the SQL statement created by SQR (which shows up in the
error
message) has one field missing.  That field is a blank (one space) that
shows up
in the SQR but not in the SQL.

Has anyone seen this kind of thing before?  The syntax looks good - right
number
of commas, etc..

Thanks,

Richard Knapp
Database Programmer/Analyst
Institutional Research and Planning
University of Missouri System
573-882-8856
knappr@umsystem.edu

_______________________________________________
sqr-users mailing list
sqr-users@sqrug.org
http://www.sqrug.org/mailman/listinfo/sqr-users

_______________________________________________
sqr-users mailing list
sqr-users@sqrug.org
http://www.sqrug.org/mailman/listinfo/sqr-users




_______________________________________________
sqr-users mailing list
sqr-users@sqrug.org
http://www.sqrug.org/mailman/listinfo/sqr-users