every time I save (ctrl+s) my pl/sql package for some reason sql developer add some white spaces between 'Package body' and the name of the package:
Can anyone tell me why this is happening or how to stop this behavior?
Thanks in advance!
Related
Occasionally I had not saved my source script, and its old version opened. I can find the new version which was executed during the previous session, but only like shreds: I search in history and it shows me a piece of code, but not all lines though they were executed simultaneously. Is there any way to access the complete history, which is definitely stored somewhere, but not shown as a whole? Thanks!
I am using R version 3.6.2 and RStudio Version 1.2.5033.
Search for the "history_database" file. It is an ASCII file and it is usually stored in the folder
C:\Users\username\AppData\Local\RStudio-Desktop
Please, take a look at: https://support.rstudio.com/hc/en-us/articles/200526217-Command-History
use shortcut key Ctrl + 4 to put focus on history or Ctrl+Shift+4 to enlarge window of history. Let us know
It seems like R studio shows me code completion suggestions from datasets that I haven't used in ages. I've searched everywhere, but can't figure out how to delete these old suggestions from the drop-down menu. Where does R get its code completion suggestions from, and how can I delete irrelevant suggestions?
In the Environment tab, click on the broom icon. You will be prompted with a dialog "confirm remove objects". If you click yes this will clear all data from the environment. If you save upon exit your will start with a clean environment.
I had created the report using report viewer in asp.net. But recently I found that it happen some error when I tried to open the excel(xlsx) file after i download. It came out with the error message
"We found a problem with some content in 'Reportest(34).xlsx'. Do you want us to try to recover as much as we can? If you trust the source of this workbook, click Yes.
After I click Yes, it have another message box pop out which is said Replaced Part: /xl/worksheets/sheet1.xml part with XML error. Illegal xml character. Line 3, column 28935.
I had tried to zip it and already find out the reason why it is error. I found that the error is because of the unreadable character in the line 28935
How do I handle this error using the error. Is that my excel version? Because previously it is working fine. Please help me to solve this problem.
Thank you
Best Regards,
Choo
I already get the solution. I added additional xls format (excel 2003) in report viewer to download and the problem is solved. The report open properly. Thanks!
I was looking here and also in Google without any luck. I hope anyone can advise something.
I need to read from the R console and I need the input not to be echoed or masked as *** or blanks.
The only thing I found is: Is it possible to read from the console with scan without echoing the characters? and I don't know how to do that.
If anyone knows a way to do this will be terrific.
Thanks in advance for your time.
There does not seem to be a native solution for R running in Windows. However, I found this terrific post which uses the tcltk package. The example generates a separate popup window into which the user can enter a masked password.
I am a novice user of Oracle Report Builder, so forgive me if the answer should be obvious.
I am attempting to run a 9i report, and I keep getting an error that appears like there is an issue with frames overlapping. I have two versions and both are getting the same error. One version is the report I want. The other is a stripped down version with only a couple fields, to narrow down what might be causing it.
Terminated with error: <br>REP-271187990: Virtual Memory System error. REP-0200: Cannot allocate enough memory. cavaa 22 REP-0002: Unable to retrieve a string from the Report Builder message file. REP-271187990:
Occasionally, it kicks out the message below when I try to run it, with no other accompanying details. The select runs and returns the desired results, and the function returns the ref cursor results as expected. The package is valid and compiled, so the query itself should be fine. There is only one query in the report, and I have tried various things, including stripping the report to narrow down the source of the error, with no luck. Any ideas to try would be appreciated.
Terminated with error: <br>REP-1401: 'qr_1refcurds1': Fatal PL/SQL error occurred.
It turns out that the problem was with data returned from my refcursor.
In the package spec I had one of the fields wrong field in the table.field%type declaration.
For those experiencing a similar error I would suggest:
If you have your SQL in functions, as opposed to right in the report, check your package spec to ensure your field order matches usage in the body.
If you have any overlapping frames in your report, this message can also come up. Check the object navigator for any hidden frames. They can be totally invisible, and the only way to know for sure is by checking in the navigator. Hint - Give meaningful names to your fields and text labels, so you can see what's contained in each frame. Also check the source of container frames is... but that's another REP error to enjoy.
Depending on setup, the first time you load a report it may error out referring to one of your queries. That happens after compile. Just try again, and every time going forward it's fine.
Consider the server patches mentioned above if your SQL statements are dynamic.
Feel free to add to this list if you know of others.
According to Oracle Support Note 430044.1 -
MS Windows: Reports 10g with Ref Cursors Fails with REP-200 and REP-65
Virtual Memory System Error [ID 430044.1]
This is a known Oracle Reports bug for MS Windows Platform.
Bug 5584001 DYNAMIC REF CURSORS DON'T WORK IN VERSION 10.1.2.0.2
REPORTS BUILDER
There are step by step instructions in the Oracle Note to apply the patch to resolve this issue. Also note, this problem is specific to MS Windows.
The suggested Oracle One-off patches are-
One-off patch 4505133
One-off patch 5634746
Log-on to Oracle Support, download the two patches and follow the step by step instructions mentioned in Note 430044.1 to apply the patch.